Venue product sales and networking

ABSTRACT

Systems, apparatus, interfaces, methods, and articles of manufacture for venue product sales and networking are provided.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims benefit and priority under 35 U.S.C.§119(e) to (i) U.S. Provisional Patent Application Ser. No. 61/294,101,filed on Jan. 11, 2010, and titled “VENDING MACHINE SYSTEMS ANDMETHODS”, and (ii) U.S. Provisional Patent Application Ser. No.61/331,208, filed on May 4, 2010, and titled “EVENT SALES ANDDISTRIBUTION SYSTEMS AND METHODS”. Each of the above-referencedapplications is hereby incorporated by reference herein.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by any-one of the patentdocument or the patent disclosure, as it appears in the Patent andTrademark Office patent file or records, but otherwise reserves allcopyright rights whatsoever.

BACKGROUND

The experiences of patrons of entertainment, sports, and other venuesare often heavily influenced by weather, availability of refreshments,and interactions with other patrons or fans. The weather, at least atoutdoor venues and/or venues not fortunate enough to be equipped withretractable roofs, is largely uncontrollable. Refreshments and/or otherproduct sales are typically conducted via either or both of concessionstands (e.g., fixed sales emplacements) and “hockers” (roaming vendorscarrying a limited selection of available products). Interactionsbetween fans are informal, disorganized, and limited to communicationswith fans proximate to each other. Improvements in how refreshments(and/or other products) are sold and/or improvements in faninteractions, could lead to increased patron satisfaction andaccordingly to increased venue revenues.

BRIEF DESCRIPTION OF THE DRAWINGS

An understanding of embodiments described herein and many of theattendant advantages thereof may be readily obtained by reference to thefollowing detailed description when considered with the accompanyingdrawings, wherein:

FIG. 1 is a block diagram of a system according to some embodiments;

FIG. 2 is a flow diagram of a method according to some embodiments;

FIG. 3 is a flow diagram of a method according to some embodiments;

FIG. 4 is a block diagram of an apparatus according to some embodiments;

FIG. 5A and FIG. 5B are perspective system diagrams of processesaccording to some embodiments;

FIG. 6A, FIG. 6B, FIG. 6C, FIG. 6D, FIG. 6E, FIG. 6F, FIG. 6G, FIG. 6H,FIG. 6I, FIG. 6J, FIG. 6K, FIG. 6L, FIG. 6M, FIG. 6N, FIG. 6O, FIG. 6 P,FIG. 6Q, FIG. 6R, FIG. 6S, FIG. 6T, FIG. 6U, FIG. 6V, FIG. 6W, FIG. 6X,FIG. 6Y, FIG. 6Z, FIG. 6AA, FIG. 6BB, FIG. 6CC, FIG. 6DD, FIG. 6EE, FIG.6FF, FIG. 6GG, FIG. 6HH, FIG. 6II, and FIG. 6JJ are example interfacesaccording to some embodiments;

FIG. 7A, FIG. 7B, FIG. 7C, FIG. 7D, FIG. 7E, FIG. 7F, FIG. 7G, FIG. 7H,FIG. 7I, and FIG. 7J are example interfaces according to someembodiments;

FIG. 8 is a block diagram of a system according to some embodiments;

FIG. 9 is a flow diagram of a method according to some embodiments;

FIG. 10 is a block diagram of an apparatus according to someembodiments; and

FIG. 11A and FIG. 11B are perspective diagrams of exemplary data storagedevices according to some embodiments.

DETAILED DESCRIPTION I. Introduction

Embodiments presented herein are descriptive of systems, apparatus,interfaces, methods, and articles of manufacture for venue product(and/or service) sales and networking. In some embodiments, for example,customers (e.g., patrons or fans) of a venue may be provided thecapability of ordering products (such as refreshments and/ormerchandise) from their seats and/or the ability to have orderedproducts delivered directly to their seats. According to someembodiments, the customers may be provided with the opportunity and/orcapability of electronic networking with other customers at the venue.

According to some embodiments, for example, methods may includereceiving (e.g., by a centralized electronic processing device) anindication of an order for a unit of a product. In some embodiments, theorder may be placed via a mobile device of a customer located at avenue. Some embodiments may include (i) determining (e.g., by thecentralized electronic processing device) a subset of a plurality offacilities at the venue, wherein each facility of the subset is capableof fulfilling the order, (ii) selecting (e.g., by the centralizedelectronic processing device and/or based on information indicative of apredicted order fulfillment time at each of the facilities of thesubset) one of the facilities of the subset to fulfill the order, (iii)transmitting (e.g., by the centralized electronic processing device) anindication of the order to the selected facility, and/or (iv)transmitting (e.g., by the centralized electronic processing deviceand/or to the mobile device of the customer) an indication of theselected facility and an indication of an expected order fulfillmenttime for the order.

According to some embodiments, methods may include receiving, after thetransmitting of the indication of the order to the selected facility, bythe centralized electronic processing device and from the selectedfacility, an indication that order is ready, and/or notifying thecustomer, via the centralized electronic processing device and inresponse to receiving the indication from the selected facility, thatthe order is ready.

In some embodiments, such as in the case that the order is adelivery-type order, methods may include notifying the customer, via thecentralized electronic processing device and in response to receivingthe indication from the selected facility, an estimated delivery time ofthe order. In some embodiments, the determining of the subset maycomprise (i) determining that an inventory level of the product at eachfacility of the subset is above a predetermined threshold, (ii)determining that each facility of the subset is authorized to providethe unit of the product, and/or (iii) determining that each facility ofthe subset has one or more of (i) sales and/or (ii) profits, that meetpredetermined threshold requirements.

According to some embodiments, the information indicative of thepredicted order fulfillment time at each of the facilities of the subsetmay comprise (i) information descriptive of a current volume of ordersat each of the facilities of the subset and/or (ii) informationdescriptive of a maximum volume of orders permitted at each of thefacilities of the subset. In some embodiments, the selecting maycomprise (i) selecting the one of the facilities of the subset tofulfill the order based on the selected one of the facilities of thesubset having the quickest predicted order fulfillment time and/or (ii)in the case that the selecting is further based on a predicted deliverytime of the order at each of the facilities of the subset, the selectingmay comprise selecting the one of the facilities of the subset tofulfill the order based on the selected one of the facilities of thesubset having the quickest predicted order fulfillment time pluspredicted delivery time.

In some embodiments, methods may include receiving, from the mobiledevice of the customer, and indication of a location of the customer atthe venue. The indication of the location may comprise, in someembodiments, an indication of one or more of (i) a GPS coordinate of thecustomer and (ii) a seat number of the customer. According to someembodiments, the selecting may comprise selecting the one of thefacilities of the subset to fulfill the order based on the selected oneof the facilities of the subset being the shortest distance from thelocation of the customer. In some embodiments, the distance may comprisea rectilinear distance between the selected facility of the subset andthe location of the customer. According to some embodiments, theselecting may comprise (i) selecting the one of the facilities of thesubset to fulfill the order based on a type of the facility and/or (ii)selecting the one of the facilities of the subset to fulfill the orderbased on a rule that specifies that browser-type facilities are to beselected first, runner-type facilities are to be selected second, andpickup-type facilities are to be selected last.

Some embodiments may include an apparatus comprising an electronicprocessor communicatively coupled to a memory device storingspecially-programmed instructions that when executed by the electronicprocessor result in execution of one or more of the methods and/orprocesses described herein. Some embodiments may include anon-transitory computer-readable memory storing specially-programmedinstructions that when executed by an electronic processing deviceresult in execution of one or more of the methods and/or processesdescribed herein.

In some embodiments, a system may comprise a network, comprising: (i) afirst communication link to a mobile electronic device operated by acustomer at a venue, (ii) a second communication link to a centralelectronic controller associated with the venue, and/or (iii) a thirdcommunication link to a fulfillment facility associated with the venue.In some embodiments, the network: (a) receives, via the firstcommunication link, an indication of an order for a unit of a product,(b) transmits, via the second communication link, the indication of theorder for the unit of the product, (c) receives, via the secondcommunication link, an indication of a selection of the fulfillmentfacility by the central electronic controller, and/or (d) transmits, viathe third communication link, the indication of the order for the unitof the product.

In some embodiments, method may include (i) determining (e.g., by anelectronic controller associated with a concession stand at a venue)information descriptive of a plurality of pending customer orders, (ii)determining (e.g., by the electronic controller) information descriptiveof a plurality of available delivery personnel, (iii) allocating (e.g.,by the electronic controller and/or based on the customer orderinformation and the delivery personnel information) the plurality ofpending customer orders amongst the plurality of available deliverypersonnel, (iv) transmitting (e.g., by the electronic controller and/orto each delivery personnel of the plurality of available deliverypersonnel that is allocated one or more customer orders) an indicationof the one or more customer orders, and/or (v) transmitting (e.g., bythe electronic controller and/or to each customer) an indication of anexpected delivery time for each customers' respective order.

In some embodiments, the information descriptive of the plurality ofpending customer orders may comprise information identifying locationsof the respective customers and wherein the allocating is further basedon rectilinear distances from the customers to the concession stand. Insome embodiments, the information identifying locations of therespective customers and wherein the information descriptive of theplurality of available delivery personnel comprises informationidentifying locations of the respective delivery personnel and whereinthe allocating is further based on rectilinear distances between thecustomers and the delivery personnel. According to some embodiments, thetransmitting of the indication of the one or more customer orders toeach of the delivery personnel of the plurality of available deliverypersonnel that is allocated one or more customer orders, may comprises(i) transmitting a list of allocated customer orders, and/or (ii)transmitting an indication of a delivery sequence for the list ofallocated customer orders. According to some embodiments, thetransmitting of the indication of the one or more customer orders toeach of the delivery personnel of the plurality of available deliverypersonnel that is allocated one or more customer orders, may comprisestransmitting a suggested rectilinear route for the delivery personnel totake when delivering the allocated customer orders on the list ofallocated customer orders.

Some embodiments may include a method, comprising (i) receiving, by anelectronic controller and from a first mobile device of a first attendeeof an event at a venue, an indication of a request to challenge a secondattendee of the event, (ii) transmitting, by the electronic controller,in response to the receiving of the indication of the challenge request,and to a second mobile device of the second attendee of the event, anindication of the challenge request, (iii) receiving, by the electroniccontroller and from the second mobile device of the second attendee ofthe event, an indication of an acceptance of the challenge request, (iv)determining, by the electronic controller, in response to the receivingof the indication of the acceptance of the challenge request, and basedon (1) stored challenge criteria relating to possible occurrences at theevent and (2) an actual occurrence at the event, whether either of thefirst or second attendees has won the challenge, (v) selecting, by theelectronic controller, a fulfillment facility at the venue that iscapable of providing a particular prize to the winner of the challenge,and/or (vi) causing, by the electronic controller, the particular prizeto be provided to the winner of the challenge via the selectedfulfillment facility at the venue.

In some embodiments, a method may comprise (i) receiving, by anelectronic controller and from a mobile device of an attendee of anevent at a venue, an indication of media captured at the event, (ii)integrating, by the electronic controller and with the media captured atthe event, media obtained from a third-party, and/or (iii) transmitting,by the electronic controller, based on saved preferences of theattendee, and via a social network associated with the attendee, anindication of the integrated media to a plurality of social networkfriends of the attendee.

In some embodiments, a system may comprise a network, comprising: (i) afirst communication link to a central electronic controller associatedwith a venue, (ii) a second communication link to a first mobile fandevice operated by a first fan of an event at the venue, and/or (iii) athird communication link to a second mobile fan device operated by asecond fan of the event at the venue. In some embodiments, the network:(a) receives, via the second communication link, an indication of mediacaptured at the event, (b) transmits, via the first communication link,the indication of media captured at the event, (c) receives, via thefirst communication link, an indication of an integration of the mediacaptured at the event with third-party media, and (d) transmits, via thethird communication link, an indication of the integration of the mediacaptured at the event with third-party media.

II. Terms and Definitions

Some embodiments described herein are associated with a “venue”. Asutilized herein, the term “venue” may be utilized to describe any typeof location or area where an event occurs. Venues may generallycomprise, for example, buildings, structures, parks, and/or other areasassociated with one or more particular events or other happenings.Venues may be of one or more types, typically based on a type of eventoccurring at the venue. “Entertainment venues”, for example, maycomprise theatres, stages, amphitheatres, parks, music halls, and/orother sites or areas where performances are held. “Sports venues” maycomprise a type of entertainment venue which may be held or conducted atany location appropriate for an entertainment venue and/or that may beheld, for example, in colosseums, stadiums, arenas, race tracks, sportsfields, ice rinks, gymnasiums, field houses, and/or other sportingareas. Venues may change type based on different types of events hostedat the venues (e.g., a “sales venue” on a day when a flea market isheld, but a sports venue on a day when a football game is held). Venuesmay typically be attended by one or more customers, patrons, or fans.

As used herein, the terms “customer”, “patron”, and “fan” may beutilized interchangeably and may generally be descriptive of anyindividual or other entity that attends an event at a venue. Customersthat purchase tickets to (and/or attend) a play in a theatre may, forexample, be referred to as patrons, or even “theatre-goers”. Customersof sporting venues such as races are typically referred to as fans(e.g., “race fans”). Venue customers may typically attend and/or watchan event from a specific area (e.g. section) or location (e.g., a seat).

As used herein, the term “section” may generally refer to a specificarea within or at a venue where a customer is located. Sections, such asin stadiums or theatres, for example, may comprise one or moreidentifiable segmentations of bleachers, boxes, tiers, terraces, stalls,balconies, galleries, and/or other areas therein. Field, club, and upperboxes and standing-room areas at a baseball stadium as well asorchestra, mezzanine, and balcony seats at a theatre are examples ofvarious sections of a venue. Typically, access to different sections isprovided to customers at different prices (e.g., court-side seats at abasketball game are much more expensive than seats in an upper deck,balcony, or back-row). Some sections may have seats or other designatedand/or specific areas for a customer to occupy, while others may not.

As used herein, the term “seat” may generally refer to any specificlocation at a venue (and/or in a specific section of a venue) for whichoccupancy by a customer may be provided (e.g., by payment of a fee).Seats may comprise actual devices or furniture for sitting, for example,and/or may comprise other designated areas for standing or for otherwiseoccupying a location at the venue. Seats may be assigned orfirst-come-first-served. Some embodiments describe how customers mayutilize mobile devices (e.g., customer devices) from their seats torealize benefits as described herein.

Some embodiments described herein are associated with a “customerdevice” or a “network device”. As used herein, a “customer device” is asubset of a “network device”. The “network device”, for example, maygenerally refer to any device that can communicate via a network, whilethe “customer device” may comprise a network device that is owned oroperated by or otherwise associated with a customer. Examples ofcustomer and/or network devices may include, but are not limited to: aPersonal Computer (PC), a computer workstation, a computer server, aprinter, a scanner, a facsimile machine, a copier, a Personal DigitalAssistant (PDA), a storage device (e.g., a disk drive), a hub, a router,a switch, and a modem, a video game console, or a wireless or cellulartelephone. Customer and/or network devices may comprise one or morenetwork components.

As used herein, the term “network component” may refer to a customerand/or network device, or a component, piece, portion, or combination ofcustomer and/or network devices. Examples of network components mayinclude, but are not limited to: a Static Random Access Memory (SRAM)device or module, a network processor, and a network communication path,connection, port, or cable.

In addition, some embodiments are associated with a “network” or a“communication network”. As used herein, the terms “network” and“communication network” may be used interchangeably and may refer to anyobject, entity, component, device, and/or any combination thereof thatpermits, facilitates, and/or otherwise contributes to or is associatedwith the transmission of messages, packets, signals, and/or other formsof information between and/or within one or more network devices.Networks may be or include a plurality of interconnected networkdevices. In some embodiments, networks may be hard-wired, wireless,virtual, neural, and/or any other configuration of type that is orbecomes known. Communication networks may include, for example, one ormore networks configured to operate in accordance with the Fast EthernetLAN transmission standard 802.3-2002® published by the Institute ofElectrical and Electronics Engineers (IEEE). In some embodiments, anetwork may include one or more wired and/or wireless networks operatedin accordance with any communication standard or protocol that is orbecomes known or practicable.

As used herein, the terms “information” and “data” may be usedinterchangeably and may refer to any data, text, voice, video, image,message, bit, packet, pulse, tone, waveform, and/or other type orconfiguration of signal and/or information. Information may compriseinformation packets transmitted, for example, in accordance with theInternet Protocol Version 6 (IPv6) standard as defined by “InternetProtocol Version 6 (IPv6) Specification” RFC 1883, published by theInternet Engineering Task Force (IETF), Network Working Group, S.Deering et al. (December 1995). Information may, according to someembodiments, be compressed, encoded, encrypted, and/or otherwisepackaged or manipulated in accordance with any method that is or becomesknown or practicable.

In addition, some embodiments described herein are associated with an“indication”. As used herein, the term “indication” may be used to referto any indicia and/or other information indicative of or associated witha subject, item, entity, and/or other object and/or idea. As usedherein, the phrases “information indicative of and “indicia” may be usedto refer to any information that represents, describes, and/or isotherwise associated with a related entity, subject, or object. Indiciaof information may include, for example, a code, a reference, a link, asignal, an identifier, and/or any combination thereof and/or any otherinformative representation associated with the information. In someembodiments, indicia of information (or indicative of the information)may be or include the information itself and/or any portion or componentof the information. In some embodiments, an indication may include arequest, a solicitation, a broadcast, and/or any other form ofinformation gathering and/or dissemination.

III. Venue Product Sales A. Overview

Referring first to FIG. 1, a block diagram of a system 100 according tosome embodiments is shown. In some embodiments, the system 100 maycomprise a controller 110 in communication with a mobile customer device130 (e.g., via a network 150). According to some embodiments, the system100 may comprise a payment device 160 and/or one or more fulfillmentdevices 170 a-n (e.g., also in communication with the network 150). Insome embodiments, any or all of the components 110, 130, 160, 170 a-n ofthe system 100 may be located (entirely or partially) at a venue 180(e.g., as depicted in FIG. 1 in accordance with some embodiments, thecontroller 110, mobile customer device 130, and fulfillment devices 170a-n are located within the venue 180).

In some embodiments, the controller 110 may, for example, comprise anelectronic and/or computerized controller device such as a computerserver communicatively coupled to interface with the mobile customerdevice 130 (directly and/or indirectly). The controller 110 may, forexample, comprise a PowerEdge™ M910 blade server manufactured by Dell®,Inc. of Round Rock, Tex. which may include one or more Eight-Core Intel®Xeon® 7500 Series electronic processing devices. According to someembodiments (such as depicted in FIG. 1), the controller 110 may belocated in (or at) the venue 180. In some embodiments, the controller110 may be located remote from the venue 180, such as at one or morecentralized locations. The controller 110 may also or alternativelycomprise a plurality of electronic processing devices located at one ormore various sites such as at the venue 180 and/or at one or more otherlocations remote from the venue 180.

According to some embodiments, the controller 110 may store and/orexecute specially programmed instructions to operate in accordance withembodiments described herein. The controller 110 may, for example,execute one or more programs that permit a customer (not explicitlyshown in FIG. 1) of the venue 180 (e.g., operating the mobile customerdevice 130) to place purchase orders for products (and/or services)available at or via the venue 180.

The mobile customer device 130, in some embodiments, may comprise anytype or configuration of mobile electronic network and/or communicationdevice that is or becomes known or practicable. The mobile customerdevice 130 may, for example, comprise a cellular and/or wirelesstelephone such as an iPhone® manufactured by Apple®, Inc. of Cupertino,Calif. or an Optimus™ S smartphone manufactured by LG® Electronics, Inc.of San Diego, Calif., and running an Androird® operating system fromGoogle®, Inc. of Mountain View, Calif. In some embodiments, such asdepicted in FIG. 1, the mobile customer device 130 may be utilized bythe customer while the customer (and thus the mobile customer device 130as well) are located at the venue 180. The customer may utilize and/oroperate the mobile customer device 130 from a section and/or seat of thevenue 180, for example, to purchase products and/or services availablefor sale at (or via) the venue 180.

The mobile customer device 130 may, for example, communicate with thecontroller 110 via the network 150 to effectuate an order and/or sale ofone or more products and/or services. In some embodiments, the mobilecustomer device 130 may interface with the controller 110 to effectuatecommunications (direct or indirect) with one or more other mobilecustomer devices 130 (not explicitly shown in FIG. 1), such as may beoperated by other customers of the venue 180. The network 150 may,according to some embodiments, comprise a LAN (wireless and/or wired),cellular telephone, Bluetooth®, and/or RF network with communicationlinks between the controller 110 and the mobile customer device 130. Insome embodiments, the network 150 may comprise direct communicationslinks between any or all of the components 110, 130, 160, 170 a-n of thesystem 100. The mobile customer device 130 may, for example, be directlyinterfaced or connected to one or more of the fulfillment devices 170a-n via one or more wires, cables, wireless links, and/or other networkcomponents within and/or associated with the venue 180, such networkcomponents (e.g., communication links) comprising portions of thenetwork 150. In some embodiments, the network 150 may comprise one ormany other links or network components other than those depicted inFIG. 1. The mobile customer device 130 may, for example, be connected tothe controller 110 via various cell towers, routers, repeaters, ports,switches, and/or other network components that comprise the Internetand/or a cellular telephone (and/or Public Switched Telephone Network(PSTN)) network, and which comprise portions of the network 150.

While the network 150 is depicted in FIG. 1 as a single object, thenetwork 150 may comprise any number, type, and/or configuration ofnetworks that is or becomes known or practicable. According to someembodiments, the network 150 may comprise a conglomeration of differentsub-networks and/or network components interconnected, directly orindirectly, by the components 110, 130, 160, 170 a-n of the system 100.The network 150 may comprise one or more cellular telephone networkswith communication links between the mobile customer device 130 and thecontroller 110, for example, and/or may comprise the Internet, withcommunication links between the controller 110 and the payment device160, for example.

In some embodiments, the payment device 160 may comprise one or moredevices including an electronic and/or computerized processing device,such as one or more web and/or computer servers (physical and/orvirtual) owned, operated by, and/or otherwise associated with afinancial entity such as a bank, credit card entity, and/or escrow-typeagent. In some embodiments, the payment device 160 may be incommunication any or all of the controller 110, the mobile customerdevice 130, and/or one or more of the fulfillment devices 170 a-n. Thepayment device 160 may, for example, communicate and/or provide paymentinformation (e.g., account numbers, account debit authorizations, creditlocks, and/or Electronic Funds Transfer (EFT) data) to facilitate theordering of products and/or services from one or more of the fulfillmentdevices 170 a-n of the venue 180, by the customer (e.g., via the mobilecustomer device 130).

According to some embodiments, the fulfillment devices 170 a-n maycomprise any type or configuration of devices, equipment, areas, and/orother objects or entities via which units of product and/or services maybe purchased at (or via) the venue 180. The fulfillment devices 170 a-nmay comprise, for example, concession stands at the venue 180 (and/orequipment and/or personnel thereof), vending machines, “smart”visi-coolers (e.g., as described in Applicants' co-pending U.S. patentapplication Ser. No. ______ filed on Jan. 7, 2011 in the name ofBreitenbach et al. and titled “SMART VISI-COOLERS”, the smartvisi-cooler descriptions and concepts of which are hereby incorporatedby reference herein), “hockers”, “runners”, and/or any devices and/orequipment utilized and/or associated therewith.

As utilized herein, the term “hocker” may generally refer to anypersonnel or other entities that offer products and/or services for salefrom non-fixed emplacements at the venue 180. Hockers may comprise, forexample, vendors carrying units of product (e.g., refreshments and/orsouvenirs) throughout various sections of the venue 180. As utilizedherein, the term “runner” may generally refer to personnel or otherentities that deliver units of product from concession stands and/orother fulfillment devices 170 a-n to a section and/or seat of a customerof the venue 180. In some embodiments, the terms “hockers” and/or“runners” may comprise any devices (such as hardware and/or electronics)that such personnel may utilize to facilitate their wandering/mobileproduct sales and/or product delivery roles. In some embodiments, ahocker may act as and/or be a runner.

In some embodiments, a customer operating the mobile customer device 130may transmit signals to the controller 110 (and/or one or more of thefulfillment devices 170 a-n), the signals being descriptive of an orderthat the customer desires to place for a product. According to someembodiments, the controller 110 may communicate with the payment device160 to acquire and/or verify payment for the order. The controller 110may, in some embodiments, determine whether to transmit signalsindicative of the order to the fulfillment devices 170 a-n. According tosome embodiments, the controller 110 may select the first fulfillmentdevice 170 a (e.g., based on inventory available at the fulfillmentdevices 170 a-n, based on order volume and/or capacity at thefulfillment devices 170 a-n, and/or based on distances between thecustomer and the various fulfillment devices 170 a-n) for fulfillment ofthe order and may accordingly transmit signals indicative of the orderto the first fulfillment device 170 a. In some embodiments, the firstfulfillment device 170 a may process the order and provide the desiredproduct(s) and/or service(s) to the customer (e.g., the customer maypickup the product in the case that the first fulfillment device 170 acomprises a concession stand, vending machine, and/or smart visi-cooler,or the product may be delivered to the customer in the case that thefirst fulfillment device 170 a comprises a hocker and/or runner).

B. Methods

Turning to FIG. 2, a flow diagram of a method 200 according to someembodiments is shown. In some embodiments, the method 200 may beperformed and/or implemented by and/or otherwise associated with one ormore specialized computerized processing devices (e.g., the controller110 and/or the mobile customer device 130 of FIG. 1), specializedcomputers, computer terminals, computer servers, computer systems and/ornetworks (e.g., the network 150 of FIG. 1), and/or any combinationsthereof. In some embodiments, the method 200 may be embodied in,facilitated by, and/or otherwise associated with various inputmechanisms and/or interfaces such as the interfaces 600, 700 describedwith respect to FIG. 6A, FIG. 6B, FIG. 6C, FIG. 6D, FIG. 6E, FIG. 6F,FIG. 6G, FIG. 6H, FIG. 6I, FIG. 6J, FIG. 6K, FIG. 6L, FIG. 6M, FIG. 6N,FIG. 6O, FIG. 6 P, FIG. 6Q, FIG. 6R, FIG. 6S, FIG. 6T, FIG. 6U, FIG. 6V,FIG. 6W, FIG. 6X, FIG. 6Y, FIG. 6Z, FIG. 6AA, FIG. 6BB, FIG. 6CC, FIG.6DD, FIG. 6EE, FIG. 6FF, FIG. 6GG, FIG. 6HH, FIG. 6II, FIG. 6JJ, FIG.7A, FIG. 7B, FIG. 7C, FIG. 7D, FIG. 7E, FIG. 7F, FIG. 7G, FIG. 7H, FIG.7I, and/or FIG. 7J herein.

The functional diagrams and flow diagrams described herein do notnecessarily imply a fixed order to any depicted actions, steps, and/orprocedures, and embodiments may generally be performed in any order thatis practicable unless otherwise and specifically noted. Any of theprocesses and methods described herein may be performed and/orfacilitated by hardware, software (including microcode), firmware, orany combination thereof. For example, a storage medium (e.g., a harddisk, Universal Serial Bus (USB) mass storage device, and/or DigitalVideo Disk (DVD)) may store thereon instructions that when executed by amachine (such as a computerized processing device) result in performanceaccording to any one or more of the embodiments described herein.

In some embodiments, the method 200 may comprise receiving an indicationof an order for a unit of a product, at 202. The order, for example, maybe placed via (e.g., transmitted from or through) a mobile device of acustomer (e.g., the mobile customer device 130 of FIG. 1) located at avenue (e.g., the venue 180 of FIG. 1) and/or may be received by anelectronic processing device such as a centralized electronic processor(e.g., the controller 110 of FIG. 1). In some embodiments, the order maycomprise an indication of payment for any desired products and/orservices. The order (or indication thereof) may, for example, comprisean identifier of a product desired for purchase as well as an identifierof a financial account to be charge for an amount equal to the purchaseprice of the product. In some embodiments, the order (or indicationthereof) may comprise an indication of a location of the customer (e.g.,a seat, section, and/or other location).

According to some embodiments, the method 200 may comprise determining(e.g., by the centralized electronic processing device) a subset of aplurality of facilities (e.g., the fulfillment devices 170 a-n ofFIG. 1) at the venue, wherein each facility of the subset is capable offulfilling the order, at 204. Software executed by aspecially-programmed electronic processing (e.g., a customer deviceand/or a controller device) may, for example, process informationindicative of the order to determine which facilities stock the desiredproduct(s), which facilities currently have stock available, whichfacilities are currently available (e.g., open for business and/or nototherwise committed—such as in the case of a hocker or runner that isbusy), and/or which facilities could benefit from more (or less) ordervolume (e.g., which facilities are over capacity and should not beselected to fulfill the order or facilities that are under capacity andcould benefit from being selected to fulfill the order).

In some embodiments, the method 200 may comprise selecting one of thefacilities of the subset to fulfill the order, at 206. The controller(or other specialized computer), for example, may utilize one or morerules and/or criteria to determine which of the available subset offacilities should be selected to fulfill the order. The selection may,in some embodiments, be based on information indicative of a predictedorder fulfillment time at each of the facilities of the subset. Thecontroller may, for example, select the facility that can (or is likelyto be able to) fulfill the order the quickest. According to someembodiments, such as in the case that the facility comprises aconcession stand, order fulfillment time may be determined based on howlong it will (or is likely to) take to prepare the order and/or how longit will (or is likely to) take for the customer to arrive at theconcession stand to acquire the order. In some embodiments, the expectedtime to delivery of the order by a hocker and/or runner may also oralternatively be utilized in selecting a fulfillment facility. In someembodiments, the proximity of various facilities to the customer may beutilized to select a facility to fulfill the order (e.g., the closestfacility to the customer's seat and/or current location).

According to some embodiments, the method 200 may comprise transmitting(e.g., by the centralized and/or other electronic processing device) anindication of the order to the selected facility (or facilities, e.g.,in the case the order is split), at 208. The controller may, forexample, transmit order details, instructions, and/or prioritizationinformation to the selected facility. In such a manner, the order may beentered into an order queue of the facility. In some embodiments, theselected facility may transmit a confirmation that is received by thecontroller, verifying that the fulfillment of the order is initiated.According to some embodiments, the facility may transmit and/or thecontroller may receive an indication of an expected order fulfillmenttime for the order. As described herein, in some embodiments the orderfulfillment time may comprise an amount of time that it takes (or isexpected to take) to prepare the order. According to some embodiments,the order fulfillment time may also or alternatively comprise an amountof time that it takes (or is expected to take) to get the completedorder to the customer (e.g., customer walking time for “pickup” orders(to the facility or roundtrip from the customer's section/seat), and/orhocker and/or runner delivery time for “delivery” orders).

In some embodiments, the method 200 may comprise transmitting (e.g., bythe centralized and/or other electronic processing device and to themobile device of the customer) an indication of the selected facilityand an indication of an expected order fulfillment time for the order,at 210. Based on information descriptive of the customer's location andthe location and/or capabilities of the selected facility, for example,the controller may determine an estimate of how long the customer maylikely have to wait for the order to be fulfilled. According to someembodiments, such as in the case that the selected facility transmitsinformation to the controller (and/or to the customer's device),information from the facility may be provided to indicate to thecustomer an expected wait time. In some embodiments, order statusupdates may be provided to the customer. The customer may be notifiedvia text-message, e-mail, voice call, and/or otherwise, for example,when the order is complete and ready to be picked up (for “pickup”orders”), when the order is complete and delivery via a hocker and/orrunner is being initiated (e.g., for “delivery” orders), and/or whendelivery personnel (e.g., a hocker and/or runner) are entering thecustomer's section and/or seat area (or other location at the venue).Status updates and/or communications with the customer may, in someembodiments, be utilized to assist delivery personnel in finding thecustomer such as by allowing the customer to speak directly with thedelivery personnel or be allowing the customer and/or delivery personnelto enter input directed toward meeting.

Referring now to FIG. 3, a flow diagram of a method 300 according tosome embodiments is shown. In some embodiments, the method 300 may beperformed and/or implemented by and/or otherwise associated with one ormore specialized computerized processing devices (e.g., the controller110 and/or the mobile customer device 130 of FIG. 1), specializedcomputers, computer terminals, computer servers, computer systems and/ornetworks (e.g., the network 150 of FIG. 1), and/or any combinationsthereof. In some embodiments, the method 200 may be embodied in,facilitated by, and/or otherwise associated with various inputmechanisms and/or interfaces such as the interfaces 600, 700 describedwith respect to FIG. 6A, FIG. 6B, FIG. 6C, FIG. 6D, FIG. 6E, FIG. 6F,FIG. 6G, FIG. 6H, FIG. 6I, FIG. 6J, FIG. 6K, FIG. 6L, FIG. 6M, FIG. 6N,FIG. 6O, FIG. 6 P, FIG. 6Q, FIG. 6R, FIG. 6S, FIG. 6T, FIG. 6U, FIG. 6V,FIG. 6W, FIG. 6X, FIG. 6Y, FIG. 6Z, FIG. 6AA, FIG. 6BB, FIG. 6CC, FIG.6DD, FIG. 6EE, FIG. 6FF, FIG. 6GG, FIG. 6HH, FIG. 6II, FIG. 6JJ, FIG.7A, FIG. 7B, FIG. 7C, FIG. 7D, FIG. 7E, FIG. 7F, FIG. 7G, FIG. 7H, FIG.7I, and/or FIG. 7J herein.

In some embodiments, the method 300 may comprise determining informationdescriptive of a plurality of pending customer orders, at 302. Anelectronic controller associated with a concession stand at a venueand/or a central controller may, for example, receive indications of theplurality of pending customer orders from one or more customers orcustomer devices. In some embodiments, such as in the case that acentral controller receives, aggregates, and/or processes customerorders, a device of a fulfillment facility (e.g., a fulfillment device170 a-n of FIG. 1) may receive such indications from the centralcontroller. According to some embodiments, the device and/or facilitythat receives the information and/or indications may comprise a deviceand/or facility selected by the central controller (e.g., at 206 in themethod 200 of FIG. 2). In some embodiments, the information descriptiveof each order of the plurality of pending customer orders may compriseinformation descriptive of a customer, one or more desired products,payment information, customer location information, order typeinformation, order priority and/or weighing information, delivery and/orpickup parameter information, suggested routing information, and/orspecial instructions.

According to some embodiments, the method 300 may comprise determining(e.g., by the electronic controller) information descriptive of aplurality of available delivery personnel, at 304. Information regardingavailable hockers, inventory carried by available hockers, hockerlocations, available runners, runner locations, delivery personnelroutes, venue congestion (e.g., in various sections and/or areas),and/or delivery personnel characteristics may be looked up, queried,received, and/or otherwise acquired. Such information may be stored byand/or acquired from a central controller and/or a fulfillment facilitydevice. Each fulfillment facility at the venue may store informationdescriptive of associated hockers and/or runners, for example. In someembodiments, one or more central controllers may store such information.In either case (or in a hybrid storage arrangement) any or allfulfillment facilities of the venue may have access to the information.

In some embodiments, the method 300 may comprise allocating theplurality of pending customer orders amongst the plurality of availabledelivery personnel, at 306. The electronic controller, for example, mayconduct the allocating based on the customer order information and thedelivery personnel information. According to some embodiments, storedinstructions may be executed that cause the allocating to be performedin a manner that minimizes and/or reduces expected fulfillment and/ordelivery or pickup times for customer orders (or for higher-prioritizedcustomer orders). In some embodiments, combinatorial optimizationtechniques know to those skilled in the art may be utilized (e.g.,“Dynamic Programming” and/or “Scheduling Production Processes”) todevelop a resource-constrained (e.g., limited number of deliverypersonnel) scheduling program. Such a program may take various factorsinto account in developing an allocation of customer orders amongstdelivery personnel. Such factors may include, but are not limited to,temporal constraints (e.g., allowed time window in which delivery mustbe completed—e.g., based on customer satisfaction and/or productcharacteristics such as spoilage parameters), procedural constraints(e.g., specific order fulfillment hierarchy, special instructions fortemperature-sensitive items, and/or other special instructions based onproduct characteristics or customer (or venue) requests), and/orresource constraints (based on the information descriptive of aplurality of available delivery personnel—such as whether a deliverypersonnel is or is scheduled to be available, on break, have time-off,etc.).

In some embodiments, scheduling and/or allocation performance may bemonitored and/or evaluated. Various parameters such as number of ordersfulfilled in a given time period, sales (and/or profit) per unit time,experienced customer wait times, inventory spoilage and/or damage,delivery distances traveled, and/or other order fulfillment metrics may,for example, be recorded, stored, and/or processed to evaluateallocation program efficiency and/or performance. In some embodiments,allocation scheme performance metrics may be utilized to enhance theallocation program. Empirical data regarding order delivery distancesmay be fed back into the allocation program, for example, to initiatechanges in the routing methods. The changes can then be evaluated todetermine of delivery distances were reduced (or not), and furtherchanges may be made on an iterative basis in an attempt to bringdelivery parameters into conformance with desired ranges and/or goals.

According to some embodiments, the method 300 may comprise transmittingan indication of the one or more customer orders, at 308. The electroniccontroller may, for example, transmit an appropriate indication to eachdelivery personnel of the plurality of available delivery personnel thatis allocated one or more customer orders. In the case that such deliverypersonnel utilize handheld electronic devices, the indications may bereceived thereat. In such a manner, for example, the delivery personnelmay be presented with an interface via which they may obtain informationdefining customer orders that the delivery personnel is required tofulfill (i.e., deliver), and order in which the orders should befulfilled, and/or a route that the delivery personnel should take tominimize delivery distances and/or times. According to some embodiments,such as in the case that a customer is a registered customer, theindication of the customer's order may include an image and/or otherlikeness of the customer (e.g., to aid the delivery personnel inlocating the customer). This may be particularly advantageous in thecase that the customer is in a non-assigned seat section of the venuesuch as in a lounge, hallway, parking lot, standing-room-only section,and/or other venue area. In some embodiments, the indication of thecustomer's order may also or alternatively comprise coordinates,directions, and/or other location information of the customer to aid thedelivery personnel in locating the customer.

In some embodiments, the method 300 may comprise transmitting anindication of an expected delivery time for each customers' respectiveorder, at 310. The electronic controller may, for example, transmit anorder status to each customer (e.g., via each customer's portableelectronic device—cell phone, tablet computer, PDA, etc.) at variouspoints in time. According to some embodiments, order status informationmay be transmitted by a delivery personnel device. Once the assigneddelivery personnel picks up the prepared and/or packaged order, forexample, the delivery personnel may push a button on their mobile deviceinterface which triggers an “order picked up for delivery” messagetransmittal to the customer. The message may, in some embodiments,include an indication of the expected delivery time. The expecteddelivery time may be calculated and/or otherwise determined based onvarious applicable factors such as the delivery personnel's location,distance (direct and/or rectilinear) to the customer, the deliverypersonnel's route, and/or the order's priority. In some embodiments,other status updates and/or order information may be provided to thecustomer (either automatically or upon customer inquiry). Once the orderis delivered to the customer, for example, an “order delivered: enjoy!”message may be transmitted to (and thus received by) the customer'smobile device. According to some embodiments, such as in the case thatdelivery personnel movements and/or locations are tracked or monitored,the controller may update expected delivery times based on updateddelivery route data (and either send automatic updates to the customeror refresh the expected time upon customer inquiry—e.g., the customerpushing a button labeled “refresh” on an interface of the customer'smobile device).

C. Apparatus

Turning to FIG. 4, a block diagram of an apparatus 410 according to someembodiments is shown. In some embodiments, the apparatus 410 may besimilar in configuration and/or functionality to the controller 110(and/or the mobile customer device 130 and/or the fulfillment devices170 a-n) as described in reference to FIG. 1 herein. The apparatus 410may, for example, execute, process, facilitate, and/or otherwise beassociated with the methods 200, 300 of FIG. 2 and/or FIG. 3 herein. Insome embodiments, the apparatus 410 may comprise a processor 412, aninput device 414, an output device 416, a communication device 418,and/or a memory device 420. Fewer or more components and/or variousconfigurations of the components 412, 414, 416, 418, 420 may be includedin the apparatus 410 without deviating from the scope of embodimentsdescribed herein.

According to some embodiments, the processor 412 may be or include anytype, quantity, and/or configuration of electronic and/or computerizedprocessor that is or becomes known. The processor 412 may comprise, forexample, an Intel® IXP 2800 network processor or an Intel® XEON™Processor coupled with an Intel® E7501 chipset, available from Intel®Corporation of Santa Clara, Calif. In some embodiments, the processor412 may comprise an electronic processor such as an Intel® Core™ 2 DuoP8600 Central Processing Unit (CPU) also available from Intel®Corporation of Santa Clara, Calif. In some embodiments, the processor412 may execute instructions, such as instructions specially programmedinto and/or for the processor 412. The execution of thespecially-programmed instructions may, for example, enable and/orfacilitate the apparatus 410 to operate in accordance with embodimentsas described herein.

In some embodiments, the processor 412 may comprise multipleinter-connected processors, microprocessors, and/or micro-engines.According to some embodiments, the processor 412 (and/or the apparatus410 and/or other components thereof) may be supplied power via a powersupply (not shown) such as a battery, an Alternating Current (AC)source, a Direct Current (DC) source, an AC/DC adapter, solar cells,and/or an inertial generator. In the case that the apparatus 410comprises a server such as a blade server, necessary power may besupplied via a standard AC outlet, power strip, surge protector, and/orUninterruptible Power Supply (UPS) device.

In some embodiments, the input device 414 and/or the output device 416are communicatively coupled to the processor 412 (e.g., via wired and/orwireless connections, traces, and/or pathways) and they may generallycomprise any types or configurations of input and output componentsand/or devices that are or become known, respectively. The input device414 may comprise, for example, a keyboard that allows an operator of theapparatus 410 to interface with the apparatus 410 (e.g., by an operatorof a central controller and/or by an employee of a fulfillment facility,such as to implement and/or interact with embodiments herein to sellproducts at venues). The output device 416 may, according to someembodiments, comprise a display screen and/or other practicable outputcomponent and/or device. The output device 416 may, for example, provideinformation, data, and/or images that permit a a delivery personneland/or fulfillment station agent to view assigned customer orders, vieworder statuses, view order priorities and/or hierarchies, view suggesteddelivery routes, customer identifying and/or location information,and/or product information (e.g., required temperature, currenttemperature, maximum delivery times, and/or handling instructions).According to some embodiments, the input device 414 and/or the outputdevice 416 may comprise and/or be embodied in a single device such as atouch-screen monitor.

In some embodiments, the communication device 418 may comprise any typeor configuration of communication device that is or becomes known orpracticable. The communication device 418 may, for example, comprise aNIC, a telephonic device, a cellular network device, a router, a hub, amodem, and/or a communications port or cable. In some embodiments, thecommunication device 418 may be coupled to provide data to a customerdevice, such as in the case that the apparatus 410 is utilized tofacilitate venue product sales via a customer's wireless and/or mobiledevice. According to some embodiments, the communication device 418 mayalso or alternatively be coupled to the processor 412. In someembodiments, the communication device 418 may comprise an IR, RF,Bluetooth™, and/or Wi-Fi® network device coupled to facilitatecommunications between the processor 412 (and/or the apparatus 410) andanother device (such as the mobile customer device 130 and/or thefulfillment devices 170 a-n, both of FIG. 1).

The memory device 420 may comprise any appropriate information storagedevice that is or becomes known or available, including, but not limitedto, units and/or combinations of magnetic storage devices (e.g., a harddisk drive), optical storage devices, and/or semiconductor memorydevices such as Random Access Memory (RAM) devices, Read Only Memory(ROM) devices, Single Data Rate Random Access Memory (SDR-RAM), DoubleData Rate Random Access Memory (DDR-RAM), and/or Programmable Read OnlyMemory (PROM). The memory device 420 may, according to some embodiments,store one or more of stadium ordering instructions 422-1 and/or orderallocation instructions 422-2. In some embodiments, the stadium orderinginstructions 422-1 and/or order allocation instructions 422-2 may beutilized by the processor 412 to provide output information via theoutput device 916 and/or the communication device 918 (e.g., thetransmitting of the indications at 208, 210 of the method 200 of FIG. 2and/or the transmitting of the indications at 308, 310 of the method 300of FIG. 3).

According to some embodiments, the stadium ordering instructions 422-1may be operable to cause the processor 412 to access and/or process oneor more of customer data 424-1, fulfillment data 424-2, and/or orderdata 424-3, as described herein (e.g., in accordance with the method 200of FIG. 2 herein). Customer data 424-1, fulfillment data 424-2, and/ororder data 424-3 received via the input device 414 and/or thecommunication device 418 may, for example, be analyzed, sorted,filtered, decoded, decompressed, ranked, scored, plotted, and/orotherwise processed by the processor 412 in accordance with the stadiumordering instructions 422-1. In some embodiments, customer data 424-1,fulfillment data 424-2, and/or order data 424-3 may be utilized by theprocessor 412 to facilitate and/or conduct processes and/or methods inaccordance with the stadium ordering instructions 422-1 to allow acustomer to purchase products and/or services from (or via) a venue asdescribed herein. The stadium ordering instructions 422-1 may, in someembodiments, interface with an application stored on and/or executed bya customer's mobile phone, for example, to facilitate the purchaseand/or delivery of venue merchandise and/or refreshments from acustomer's seat (or other location).

According to some embodiments, the order allocation instructions 422-2may be operable to cause the processor 412 to access and/or process oneor more of customer data 424-1, fulfillment data 424-2, and/or orderdata 424-3, as described herein (e.g., in accordance with the method 300of FIG. 3 herein). Customer data 424-1, fulfillment data 424-2, and/ororder data 424-3 received via the input device 414 and/or thecommunication device 418 may, for example, be analyzed, sorted,filtered, decoded, decompressed, ranked, scored, plotted, and/orotherwise processed by the processor 412 in accordance with the orderallocation instructions 422-2. In some embodiments, customer data 424-1,fulfillment data 424-2, and/or order data 424-3 may be utilized by theprocessor 412 to facilitate and/or conduct processes and/or methods inaccordance with the order allocation instructions 422-2 to allocatecustomer orders to fulfillment stations and/or delivery personnel asdescribed herein. The order allocation instructions 422-2 may, in someembodiments, interface with an application stored on and/or executed bya mobile device of delivery personnel, for example, to facilitate theload-balancing of orders within a venue and/or to facilitate thedelivery of venue merchandise and/or refreshments to a customer's seat(or other location).

In some embodiments, the customer data 424-1 may comprise any datadescriptive of an attribute or characteristic of a customer. Customerdata 424-1 may be acquired during a registration processes (e.g., fromthe customer), for example, and may comprise identifying informationsuch as address, name, e-mail address, preferences, payment accountsand/or information, passwords, etc. In some embodiments, the customerdata 424-1 may comprise data decretive of the customer that is acquiredvia transactions conducted with the customer. Customer data 424-1 maycomprise, for example, customer preferences (empirical), sales history,customer “worth” (e.g., expected value), frequency of purchases, and/orprevious or typical ordering locations (e.g., season ticket reserved boxseats).

According to some embodiments, the fulfillment data 424-2 may comprisedata descriptive of one or more fulfillment facilities, stations, and/orpersonnel at (or associated with) the venue. The fulfillment data 424-2may comprise, for example, data descriptive of fulfillment facilityinventory, order preparation and/or packaging statistics (e.g., averageorder preparation time), sales metrics (e.g., total sales volume,profits, sales and/or profit goals), fulfillment location information(e.g., coordinates, best/quickest routes to and/or from the location,nearby and/or typically served sections and/or seats), fulfillmentstation capacity information (e.g., maximum customer and/or order queuelength, order volume capacity, current capacity and/or queue length,and/or staffing levels), and/or hocker and/or runner metrics (e.g.,inventory carried, average delivery times to different sections/seats,history of proper handling of certain types of goods, and/oravailability).

In some embodiments, the order data 424-3 may comprise informationdescriptive of one or more customer orders. The order data 424-3 may,for example, comprise an identification of desired products and/orservices, payment information (e.g., an indication that the order hasbeen paid for and/or an indication of how the order is to be paid for),delivery instructions, customer location information, special handling,preparation, and/or packaging instructions, and/or order priority and/orhierarchy information (e.g., based on First-In-First-Out (FIFO) orderfulfillment and/or queuing and/or based on customer ranking orrating—e.g., customers with higher expected values (such as based onexpected sales to the customer) may have higher prioritized orders).

While the apparatus 410 is described with reference to specificquantities and types of components 412, 414, 416, 418, 420, variationsin the quantities, types, and/or configurations of the components 412,414, 416, 418, 420 of the apparatus 410 may be implemented withoutdeviating from the scope of the embodiments described herein.

D. Processes

Referring now to FIG. 5A and FIG. 5B, functional perspective diagrams ofprocesses 500, 502 according to some embodiments are shown. In someembodiments, the processes 500, 502 may be performed and/or implementedby and/or otherwise associated with one or more specialized computerizedprocessing devices (e.g., the controller 110, mobile customer device130, and/or fulfillment devices 170 a-n of FIG. 1 and/or the apparatus410 and/or processor 412 of FIG. 4 herein), specialized computers,computer terminals, computer servers, computer systems and/or networks,and/or any combinations thereof (e.g., by one or more venue salescomputers, networks, controllers, and/or processing devices). In someembodiments, the processes 500, 502 may be related to and/or comprisemethods for sales at venues such as described in accordance with themethods 200, 300 of FIG. 2 and/or FIG. 3 herein. In some embodiments,the processes 500, 502 may be embodied in, facilitated by, and/orotherwise associated with various input mechanisms and/or interfaces asdescribed herein.

According to some embodiments, the processes 500, 502 may comprisevarious procedures performed in association with a controller 510(comprising a communication device 518, a first database 520-1, a seconddatabase 520-2, and/or a third database 520-3), a mobile customer device530, a plurality of customers 532-1, 532-2, 532-3, 532-4, 532-5, and/ora plurality of fulfillment facilities 570-1, 570-2, 570-3, 570-4, 570-5.In some embodiments, the controller 510, mobile customer device 530,plurality of customers 532-1, 532-2, 532-3, 532-4, 532-5, and/or theplurality of fulfillment facilities 570-1, 570-2, 570-3, 570-4, 570-5may be physically located within or at a venue 580 (such as a sportsstadium or arena as depicted in FIG. 5A and FIG. 5B). According to someembodiments, fewer or more components 510, 520, 530, 532, 570, 580and/or various configurations of the depicted components 510, 520, 530,532, 570, 580 may be included in execution of the processes 500, 502without deviating from the scope of embodiments described herein. Insome embodiments, the components 510, 520, 530, 532, 570, 580 may besimilar in configuration and/or functionality to similarly named and/ornumbered components as described with reference to system 100 of FIG. 1,the methods 200, 300 of FIG. 2 and/or FIG. 3, and/or the apparatus 410of FIG. 4 herein.

In some embodiments, the first process 500 of FIG. 5A may comprise atransmission sent from the first customer 532-1 (and/or a deviceoperated by the first customer 532-1; not explicitly shown) and receivedby the controller 510, at 590-1. The transmission may comprise, forexample, a request to purchase a unit of a product, paymentauthorization, location information, and/or account or other informationdescriptive of the first customer 532-1 and/or a first order placed bythe first customer 532-1. The transmission may comprise an indication ofa product identified by the customer. The customer may utilize a mobiledevice, for example, to select and/or enter a Stock-Keeping Unit (SKU),picture, and/or barcode such as a Universal Product Code (UPC)descriptive of the desired product (or service), such as by browsingthrough an interface menu of available products and/or services andassociated identifiers.

According to some embodiments, the first process 500 of FIG. 5A maycomprise a transmission sent from the second customer 532-2 (and/or themobile customer device 530 depicted as being associated therewith) andreceived by the controller 510, at 590-2. In some embodiments, the firstprocess 500 of FIG. 5A may comprise a transmission sent from the thirdcustomer 532-3 (and/or a device operated by the first customer 532-3;not explicitly shown) and received by the controller 510, at 590-3. Insome embodiments, the first process 500 of FIG. 5A may comprise atransmission sent from the fourth customer 532-4 (and/or a deviceoperated by the first customer 532-4; not explicitly shown) and receivedby the controller 510, at 590-4.

As depicted in FIG. 5A, any or all of the transmissions from thecustomers 532 and/or information associated therewith may be stored inthe first database 520-1, which may, for example, be referred to as an“order” database (or a “customer” database). In some embodiments, theinformation received from the customers 532 may comprise informationsimilar to the customer data 424-1 and/or the order data 424-3 describedin reference to FIG. 4 herein and/or may be similar to the informationdescribed in reference to the procedures at 202, 302 of the methods 200,300 of FIG. 2 and/or FIG. 3 herein. In some embodiments, fewer or moredata elements and/or data fields than are shown and/or described may beassociated with the databases described herein. Only a portion of one ormore databases and/or other data stores is necessarily shown and/ordescribed herein, for example, and other database fields, columns,structures, orientations, quantities, and/or configurations may beutilized without deviating from the scope of some embodiments.Similarly, the data shown and/or described in the various data elements,types, and/or fields is provided solely for exemplary and illustrativepurposes and does not limit the scope of embodiments described herein.

According to some embodiments, the first process 500 of FIG. 5A maycomprise a transmission sent from the first fulfillment facility 570-1and received by the controller 510, at 592-1. In some embodiments, theinformation may not be transmitted, but instead may be provided,looked-up, and/or otherwise acquired by the controller 510. As depictedin FIG. 5A for purposes of example only, the first fulfillment facility570-1 comprises a concession stand at the venue 580. In someembodiments, the information received (and/or otherwise determined) bythe controller 510 at 592-1 may comprise information descriptive of theconcession stand 570-1. The information may comprise, for example,information descriptive of a current state of pending orders, orderfulfillment data, staffing information, inventory information, and/orsales information (e.g., how close the concession stand 570-1 is tosales and/or profit goals and/or how much change the concession stand570-1 has on hand).

In some embodiments, the first process 500 of FIG. 5A may comprise atransmission sent from the second fulfillment facility 570-2 andreceived by the controller 510, at 592-2. As depicted in FIG. 5A forpurposes of example only, the second fulfillment facility 570-2comprises a hocker at the venue 580. In some embodiments, theinformation received (and/or otherwise determined) by the controller 510at 592-2 may comprise information descriptive of the hocker 570-2. Theinformation may comprise, for example, information descriptive of theavailability of the hocker 570-2 (e.g., is the hocker 570-2 busy ornot), information descriptive of any inventory carried by the hocker570-2, an indication of the location of the hocker 570-2 (e.g.,coordinates, section number, seat number, and/or distance from one ormore waypoints or destinations), and/or an indication of a status of thehocker 570-2 (e.g., does the hocker 570-2 need a break or rest, how longhas the hocker 570-2 been deployed, and/or biometric informationdescriptive of the hocker 570-2—e.g., heart rate, etc.).

According to some embodiments, the first process 500 of FIG. 5A maycomprise a transmission sent from the third fulfillment facility 570-3and received by the controller 510, at 592-3. As depicted in FIG. 5A forpurposes of example only, the third fulfillment facility 570-3 comprisesa smart visi-cooler at the venue 580. In some embodiments, theinformation received (and/or otherwise determined) by the controller 510at 592-3 may comprise information descriptive of the smart visi-cooler570-3. The information may comprise, for example, informationdescriptive of inventory levels in the smart visi-cooler 570-3, anoperational status of the smart visi-cooler 570-3 (e.g., any errors,temperature settings, and/or whether the door is opened or closed),and/or an indication of how many customers are waiting in line at thesmart visi-cooler 570-3 (e.g., a length of a sales queue at the smartvisi-cooler 570-3).

In some embodiments, the first process 500 of FIG. 5A may comprise atransmission sent from the fourth fulfillment facility 570-4 andreceived by the controller 510, at 592-4. As depicted in FIG. 5A forpurposes of example only, the fourth fulfillment facility 570-4comprises a runner at the venue 580. In some embodiments, theinformation received (and/or otherwise determined) by the controller 510at 592-4 may comprise information descriptive of the runner 570-4. Theinformation may comprise, for example, information descriptive of theavailability of the runner 570-4 (e.g., is the runner 570-4 busy ornot), information descriptive of any inventory carried by the runner570-4, an indication of the location of the runner 570-4 (e.g.,coordinates, section number, seat number, and/or distance from one ormore waypoints or destinations), and/or an indication of a status of therunner 570-4 (e.g., does the runner 570-4 need a break or rest, how longhas the runner 570-4 been deployed, and/or biometric informationdescriptive of the runner 570-4—e.g., heart rate, etc.).

As depicted in FIG. 5A, any or all of the transmissions from thefulfillment facilities 570 and/or information associated therewith maybe stored in the second database 520-2, which may, for example, bereferred to as a “fulfillment facility” database. In some embodiments,the information received from the fulfillment facilities 570 maycomprise information similar to the fulfillment data 424-2 described inreference to FIG. 4 herein and/or may be similar to the informationdescribed in reference to the procedures at 204, 304 of the methods 200,300 of FIG. 2 and/or FIG. 3 herein. The information may be relativelystatic, such as information descriptive of a location of afixed-placement concession stand or smart visi-cooler, or informationregarding what types of products the concession stand usually stocks, orthe information may be dynamic, such as the current location of a runneror hocker, current inventory levels (e.g., of a concession stand, smartvisi-cooler, and/or hocker), current status, etc.

In some embodiments, the second process 502 of FIG. 5B may comprise atransmission sent from the controller 510 and received by the hocker570-2, at 594-1. The controller 510 may, for example, allocate thevarious orders from the customers 532 amongst the various fulfillmentfacilities 570. As depicted in FIG. 5B, for example, the controller 510may store order allocation information in the third database 520-3. Asan example, the first order of the first customer 532-1 may comprise a“delivery” type order and may be assigned to the hocker 570-2. In someembodiments, the first order may be assigned to the hocker 570-2 becauseit is determined that the hocker 570-2 has appropriate inventory tofulfill the order and/or because the hocker 570-2 is currently locatedin the same section as the first customer 532-1. In some embodiments,the hocker 570-2 may be selected as being the fastest possiblyfulfillment facility 570 for fulfilling the first order (e.g., becausethe hocker 570-2 is the closest fulfillment facility 570 to the firstcustomer 532-1 and/or the closest fulfillment facility 570 that iscapable of fulfilling the first order). In some embodiments, thetransmission at 594-1 may include providing data descriptive of thefirst order and/or the first customer 532-1. The information maycomprise, for example, information informing the hocker 570-2 that thefirst order has been assigned to the hocker 570-2, informationindicating quantities and/or types of products purchased, informationindicating where the first customer 532-1 is located (and/or identifyinganother location where the order should be delivered), what the firstcustomer 532-1 looks like and/or is wearing, and/or priority or routinginformation associated with the first order.

According to some embodiments, the second process 502 of FIG. 5B maycomprise a transmission sent from the controller 510 and received by therunner 570-4, at 594-2. The controller 510 may allocate the second orderfrom the second customer 532-2 to the runner 570-4, for example, andstore information descriptive of the allocation in the third database520-3 (as shown).

In some embodiments, the second process 502 of FIG. 5B may comprise atransmission sent from the controller 510 and received by the smartvisi-cooler 570-3, at 594-3. As depicted, for example, the controller510 may allocate the third order from the third customer 532-3 to thesmart visi-cooler 570-3. In some embodiments, the transmission at 594-3may include information informing the smart visi-cooler 570-3 of theassigned third order such as information identifying the third customer532-3 that will be picking up the desired product(s) at the smartvisi-cooler 570-3. In some embodiments, the information may comprise acode, password, account number, picture of the third customer 532-3,and/or other information that permits the smart visi-cooler 570-3 toverify (i) that an accessing of the smart visi-cooler 570-3 is conductedby the third customer 532-3 (e.g., as opposed to another customer 532)and/or (ii) that the third customer 532-3, upon accessing the smartvisi-cooler 570-3, removes the correct type and/or quantity of productfrom the smart visi-cooler 570-3.

According to some embodiments, the second process 502 of FIG. 5B maycomprise a transmission sent from the controller 510 and received by theconcession stand 570-1, at 594-4. The controller 510 may allocate thefourth order from the fourth customer 532-4 to the concession stand570-1, for example, and store information descriptive of the allocationin the third database 520-3 (as shown). In some embodiments, theconcession stand 570-1 may be selected to fulfill the fourth order,despite being near the opposite side of the venue 580. Other closerfulfillment facilities 570 may not, for example, have the correctinventory to fill the order, may be understaffed and/or too busy, mayhave already achieved sales and/or profit goals, and/or may actually bemore difficult to access by the fourth customer 532-4 (e.g., the fourthcustomer 532-4 may be handicapped and the concession stand 570-1 may bethe closest (or only) handicapped-accessible fulfillment facility 570and/or a route to the concession stand 570-1 may be easier and/orquicker to travel (e.g., less congestion, fewer turns, and/or may haveelevators and/or handicapped-access ramps) than routes to nearerfulfillment facilities 570 (not explicitly shown).

In some embodiments, information transmitted (and/or otherwise provided)to the fulfillment facilities 570 (e.g., at 594-1, 594-2, 594-3, and/or594-4) may include information descriptive of one or more suggestedroutes 596 via which orders may be fulfilled (e.g., routes 596 thatcustomers 532 may take to pick-up ordered products and/or routes 596that delivery personnel 570-2, 570-4 may take to deliver products tocustomers 532). The first transmission at 594-1, for example, maycomprise information descriptive of a first route 596-1 that the hocker570-2 may take to locate and/or deliver products and/or services to thefirst customer 532-1. According to some embodiments, the first route596-1 may be determined (e.g., by the controller 510) to have theshortest distance and/or shortest travel time amongst available routingoptions. In some embodiments, the first route 596-1 may comprise one ormore best available (e.g., shortest distance and/or shortest time)rectilinear (e.g., “Manhattan” or “taxi-cab”) routes (e.g., taking intoaccount available aisles, section layouts, seating configurations,etc.).

According to some embodiments, the information made available to thehocker 570-2 may also or alternatively comprise information descriptiveof a second route 596-2. The second route 596-2 may, for example,comprise a longer path but may, for example, pass by a fifth customer532-5 that needs assistance, has also ordered a product stocked by thehocker 570-2 (e.g., an additional sales and/or fulfillment opportunity),and/or that is known (e.g., by the controller 510) to have a history ofordering from hockers.

In some embodiments, the second transmission 594-2 to the runner 570-4may include an indication of a third route 596-3. The third route 596-3may, for example, comprise a path that takes the runner 570-4 near afifth fulfillment facility 570-5 which may comprise a product pickuplocation and/or repository (e.g., a location where hockers and/orrunners may re-stock and/or pickup units of product fordistribution—e.g., to fulfill allocated customer orders).

According to some embodiments, while not explicitly depicted in FIG. 5Aor FIG. 5B, other transmissions and/or provisions of information may beincluded in the processes 500, 502. Once an order is allocated to afulfillment facility 570 and/or a fulfillment facility 570 acknowledgesassignment of the order, the associated customer 532 may be notifiedthat order fulfillment has been initiated, delivery has been initiated,order preparation is complete and the order is ready for pick-up.

The transmissions and/or flow of data between the controller 510, thecustomers 532 (and/or mobile customer devices 530), and/or fulfillmentfacilities 570 may be accomplished via one or more network connectionsand/or communication links between such components 510, 530, 532, 570.While a network (such as the network 150 of FIG. 1) is not explicitlyshown in FIG. 5A or FIG. 5B, for example, it should be understood thatthe described communications may occur over, through, and/or via such anetwork and/or may be facilitated by one or more network componentsthereof.

E. Interfaces

Turning now to FIG. 6A, FIG. 6B, FIG. 6C, FIG. 6D, FIG. 6E, FIG. 6F,FIG. 6G, FIG. 6H, FIG. 6I, FIG. 6J, FIG. 6K, FIG. 6L, FIG. 6M, FIG. 6N,FIG. 6O, FIG. 6 P, FIG. 6Q, FIG. 6R, FIG. 6S, FIG. 6T, FIG. 6U, FIG. 6V,FIG. 6W, FIG. 6X, FIG. 6Y, FIG. 6Z, FIG. 6AA, FIG. 6BB, FIG. 6CC, FIG.6DD, FIG. 6EE, FIG. 6FF, FIG. 6GG, FIG. 6HH, FIG. 6II, and FIG. 6JJ,example interfaces 600 according to some embodiments are shown. In someembodiments, the interfaces 600 may comprise a web page, web form,database entry form, Application Program Interface (API), spreadsheet,table, and/or application or other Graphical User Interface (GUI), suchas a smart phone application. The interfaces 600 may, for example, beutilized by a customer and may facilitate the customer's purchase ofproducts and/or services at a venue as described herein. The interfaces600 may, for example, comprise portions of a venue product salesapplication and/or platform programmed and/or otherwise configured toexecute, conduct, and/or facilitate any of the various methods 200, 300of FIG. 2, and/or FIG. 3 and/or the process 500, 502 of FIG. 5A and/orFIG. 5B, and/or portions or combinations thereof. In some embodiments,the interfaces 600 may be output via one or more computerized devicesuch as the mobile customer device 130, 530 of FIG. 1 and/or FIG. 5Aand/or FIG. 5B herein.

According to some embodiments, the interface 600 shown in FIG. 6A, maycomprise an interface screen that allows a customer to register forvenue product and/or service sales. As depicted, for example, theinterface 600 may provide functionality to allow the customer to entere-mail, password, and/or other login information and/or may permit thecustomer to create a new account with an entity that manages and/orfacilitates venue product sales (e.g., with the controller 110, 510 ofFIG. 1 and/or FIG. 5A and/or FIG. 5B herein). As depicted in FIG. 6B,the customer may enter registration information into the interface 600.In some embodiments, as depicted in FIG. 6C, the customer may also oralternatively be prompted to enter a mobile telephone number and/orother mobile device identification information (e.g., informationassociated with the mobile customer device 130, 530 of FIG. 1 and/orFIG. 5A and/or FIG. 5B herein).

According to some embodiments (as depicted in FIG. 6D), the interface600 may prompt the customer to enter a name, nickname, account name,and/or “handle”. Such information may be utilized, for example, tofacilitate communications with the customer (e.g., the hocker 570-2 ofFIG. 5A and/or FIG. 5B may utilize the customer's name or handle tolocate the customer (e.g., in a crowd), such as by calling thecustomer's name in a specific section of a venue, and/or to properlyaddress the customer once located. In some embodiments (as depicted inFIG. 6E), the interface 600 may comprise a form via which the customermay enter credit card and/or other payment information to be associatedwith the customer's venue product sales account. As shown in FIG. 6F, insome embodiments the customer may enter credit card information such asby selecting the appropriate credit card type from a drop-down listand/or by entering the appropriate credit card account identifier(s). Insome embodiments, such as depicted in FIG. 6G, the interface 600 mayprovide a registration confirmation screen that may, for example, givethe customer an opportunity to read any applicable terms and conditions,privacy policies, etc. In the case that the customer indicates anacceptance of any applicable terms and conditions, the interface 600 mayprovide an indication that the registration is being processed, such asshown in FIG. 6H.

According to some embodiments, such as in the case that the customer isalready registered and/or has just finished the registration process,the customer may utilize the interface 600 to initiate a product (and/orservice) purchase at (and/or via) the venue (depicted in FIG. 6I). Theinterface 600 may, in some embodiments, provide the customer withoptions to select a nearby venue (e.g., based on location informationassociated with the customer) and/or to browse available venues by thestate and or region within which the customer is attending an event at avenue such as a sports stadium. As depicted in FIG. 6I, for example, theinterface 600 may prompt the customer to select the nearby “Stadium VIP”or browse available venues via one of “California”, “Connecticut”, and“D.C.” (e.g., the District of Columbia).

In some embodiments, such as in the case that the customer selects thenearby “Stadium VIP”, a confirmation screen may be provided (as depictedin FIG. 6J) that affords the customer the opportunity to confirm theselection or go back to the venue selection screen. According to someembodiments (as depicted in FIG. 6K), once the venue (e.g., stadium) isselected, the customer may select, enter, and/or otherwise indicatewhere in the venue the customer is located. As shown in FIG. 6K, thecustomer may enter a section, row, and/or seat number (e.g., forassigned-seating venues and/or venues having identifiable seats and/orlocations) into and/or via the interface 600. In some embodiments, thecustomer's location may automatically be determined and/or entered bythe customer (e.g., in the case that the customer is not in an assignedand/or identifiable seat). According to some embodiments, the customermay utilize a mobile device to take a picture and/or video of thecustomer's surroundings so that the customer's location can bedetermined (e.g., by a controller and/or delivery personnel). In someembodiments, such as in the case that the customer selects “Section 12,Row A, Seat 1”, a confirmation screen may be provided (as depicted inFIG. 6L) that affords the customer the opportunity to confirm thecustomer' location or go back to the location selection screen.

In some embodiments (as depicted in FIG. 6M), the interface 600 mayindicate to the customer that the customer's “session” is beingactivated. The customer's registration information, account information,location information, and/or venue specific menus and/or interfacescreens or options may, for example, be processed and/or loaded onto thecustomer's mobile device. As an example, the menu options depicted inFIG. 6N may be presented to the customer via the interface 600 and may,for example, be tailored, customized, and/or otherwise based on thespecific venue (e.g., “Stadium VIP”) and/or the customer. As shown inFIG. 6N, the customer may select a “Merchandise” menu, a “Food & Drinks”menu, a “help” menu, a “settings” menu, and/or select to “exit” thestadium (e.g., an option to deselect the selected venue within theapplication that generates and/or presents the interface 600).

In some embodiments (such as depicted in FIG. 6O), such as in the casethat the customer selects the “Merchandise” menu, the interface 600 maycomprise a display via which the customer may browse through and/orselect various merchandise for sale at (or via) the venue. As depictedin FIG. 6O, for example, the customer may select a “Home/Off” (e.g.,home and office) menu category and browse through products categorizedthere under—such as the Oakland Athletics™ recliner as shown. Accordingto some embodiments (as depicted in FIG. 6P), the customer may choosethe “Jerseys” category to view available sports jerseys. The customermay also or alternatively narrow the category selection be selecting oneof “Male”, “Female”, or “Kids” (e.g., the men's “authentic” jersey isshown in FIG. 6P).

According to some embodiments, the customer may select a “Caps/Hats”category (as depicted in FIG. 6Q) and the “Female” subcategory to browseto and/or identify the “siren women's cap” as shown. In someembodiments, as instructed by the interface 600, the customer may tap(e.g., select) the image of the cap to add a unit of the selectedproduct to the customer's virtual shopping cart. As shown in FIG. 6Q,for example, the numeral one (1) may appear in the product picturedisplay area to indicate that the customer has added one (1) unit of theselected cap to the customer's shopping cart.

In some embodiments, such as when an error occurs (as depicted in FIG.6R), an error screen may be displayed via the interface 600. As shown inFIG. 6R, for example, the cap selected for purchase by the customer isnot available and the customer is prompted to remove the item from thevirtual shopping cart and to select a different product for purchase. Asan example, the customer may then select a “women's replica jersey” asdepicted in FIG. 6S. In some embodiments, such as in the case that anitem requiring order details is selected for purchase (e.g., such as thewomen's replica jersey), an order details section screen, such as thesize selection screen depicted in FIG. 6T, may be presented to thecustomer. In some embodiments, once any order details are selectedand/or otherwise defined, the desired item(s) may be added to thecustomer's virtual shopping cart, as shown in FIG. 6U. According to someembodiments, the customer may enter payment information and/or paymentconfirmation information, such as the customer's billing zip code, asdepicted in FIG. 6V. In some embodiments, such as in the case that thecustomer indicates a desire to consummate the order (e.g., by pressing a“submit” button—not explicitly shown), the interface 600 may indicate(e.g., via a processing status screen such as shown in FIG. 6W) a statusof the processing and/or consummation of the order.

In some embodiments, the interface 600 may provide the customer with alist of pending orders (e.g., orders submitted and/or paid for) via apending order screen such as is depicted in FIG. 6X. The pending orderscreen may, for example, show (i) a line-item (or other object)representing the order for the women's jersey, (ii) an indication of thefulfillment facility at (or associated with) the venue that has beenassigned the order (e.g., the “concession #100”), and/or (iii) anestimate of the time to packaging, preparation, fulfillment, and/ordelivery of the order. In some embodiments, the order may be assigned acolor, code, picture, image, and/or other identifier, such as theinitials “AJZ” as shown in FIG. 6X.

According to some embodiments, the interface 600 may comprise afull-screen view of an order and/or order details, such as depicted inFIG. 6Y. The full-screen view of the order may be presented to thecustomer, for example, in the case the customer selects (e.g., touchesthe line-item representing) the order from the list of pending orderspresented in FIG. 6X. As depicted in FIG. 6Y, the order detail screenmay, in some embodiments, present the order identifier (e.g., “AJZ”), anindication of the customer's seat number and/or location, an indicationof whether the order is a “pickup” or “delivery” type order, and/or anindication of when the order will be ready/delivered (e.g., expectedfulfillment time).

As another example of how the interface 600 may be utilized inaccordance with some embodiments, FIG. 6Z depicts a customer viewing aproduct screen for a hot dog (e.g., from the “food” category). In someembodiments, the customer may select the hot dog for purchase (e.g., adda hot dog to the customer's virtual shopping cart) by tapping thepicture/image of the hot dog. As shown in FIG. 6AA, for example, thecustomer may have tapped the image of the hot dog twice (and/orotherwise indicated a desire to purchase two hot dogs), such as isindicated by the number two (2) shown next to and/or on the image of thehot dog.

In a continuance of the example, the customer may then navigate to theproduct screen for a twenty-ounce (20 oz.) Coca-Cola® (e.g., from the“Soda” category), as depicted by FIG. 6BB, and also add two units of thedesired product to the customer's virtual shopping cart. According tosome embodiments, such as in the case the customer selects the “Go toCart” button, a virtual shopping cart screen (as depicted in FIG. 6CC)may be displayed. The virtual shopping cart screen may list items addedto the cart by the customer, for example, as well as prices. As shown inFIG. 6CC, the virtual shopping cart screen may include a “Checkout”button which may, in some embodiments and upon selection by thecustomer, cause the interface 600 to display a processing status screenas depicted in FIG. 6DD.

In some embodiments, such as in the case that the order from FIG. 6CCand/or FIG. 6DD is consummated (e.g., processed, verified, submitted,and/or paid for), the interface 600 may present an order list screen,such as is depicted in FIG. 6EE. The order list screen may include alisting of any outstanding (e.g., pending) orders, for example, such asthe order for the Coca-Cola® sodas and the hot dogs, an identifier of anassigned fulfillment location/facility (e.g., “Concession #112”), and/oran estimated order fulfillment time. According to some embodiments, suchas depicted in FIG. 6FF, an e-mail (and/or other communication) may besent to the customer (and/or the customer's mobile device) alerting thecustomer of the placement of the order and/or summarizing order detailssuch as cost, ordered items, transaction and/or receipt identifiers,and/or instructions regarding order fulfillment.

In some embodiments, such as shown in FIG. 6GG, the interface 600 mayprovide a screen identifying the placed order and/or details thereof.Information identifying the order (e.g., “AKJ”), the customer's location(e.g., seat, section, and/or coordinates), information identifying thefulfillment method (e.g., pickup or delivery), and/or informationindicating the estimated time to fulfillment may, for example, beincluded. In some embodiments, such as in the case that the status ofthe order changes, an order status change screen (as depicted in FIG.6HH) may be presented via the interface 600. As shown in FIG. 6HH, forexample, the order status change screen may indicate that the order hasbeen prepared and/or packaged and has been picked up by a runner and/orhocker for delivery to the customer's location. While the message of thestatus change depicted in FIG. 6HH may, in some embodiments, beillustrative of a message from an application running on the customer'smobile device, other notification methods are also or alternativelycontemplated. As shown in FIG. 6II, for example, the status changenotification may be sent via text message (e.g., via Short MessageService (SMS)) to the customer's device. In some embodiments, such as inthe case that the order is picked up by the customer, delivered to thecustomer, and/or otherwise fulfilled or closed, the interface 600 maydisplay a status update screen informing the customer that the order iscomplete (as shown in FIG. 6JJ).

Turning now to FIG. 7A, FIG. 7B, FIG. 7C, FIG. 7D, FIG. 7E, FIG. 7F,FIG. 7G, FIG. 7H, FIG. 7I, and FIG. 7J, example interfaces 700 accordingto some embodiments are shown. In some embodiments, the interfaces 700may comprise a web page, web form, database entry form, API,spreadsheet, table, and/or application or other GUI, such as a POSapplication. The interfaces 700 may, for example, be utilized by anemployee of a product and/or service fulfillment station to facilitate acustomer's purchase of products and/or services at a venue as describedherein, and/or to facilitate distribution and/or delivery of suchpurchases to the customer as described herein. The interfaces 700 may,for example, comprise portions of a venue product sales applicationand/or platform programmed and/or otherwise configured to execute,conduct, and/or facilitate any of the various methods 200, 300 of FIG.2, and/or FIG. 3 and/or the process 500, 502 of FIG. 5A and/or FIG. 5B,and/or portions or combinations thereof. In some embodiments, theinterfaces 700 may be output via one or more computerized device such asthe controller 110, 510 of FIG. 1 and/or FIG. 5A and/or FIG. 5B, theapparatus 410 of FIG. 4, and/or any or all of the fulfillment devices170 a-n, 570 of FIG. 1 and/or FIG. 5A and/or FIG. 5B, herein.

According to some embodiments, the interface 700 shown in FIG. 7A, maycomprise a screen of a POS system and/or software program or application(and/or of a controller application). The interface 700 may, forexample, be powered and/or generated by a specially-programmedapplication that allows POS devices, components, and/or personnel (e.g.,of a fulfillment facility 170 a-n, 570 of FIG. 1 and/or FIG. 5 herein)to accept orders from customers (e.g., routed through and/or processedby a controller) for products and/or service at (and/or via) a venue(e.g., a venue where the POS is located). As shown in FIG. 7A, forexample, the “User Administration” screen may allow POS personnel tocreate, edit, and/or manage preferences and/or settings descriptive ofaccounts for personnel that will or may interact with and/or utilize theinterface 700 to accept, process, and/or fulfill customer orders. Insome embodiments, such as in the case that personnel already have anaccount created (and/or create an account via the interface 700 of FIG.7A), the personnel may login to the software and/or interface 700, suchas by utilizing the login screen depicted in FIG. 7B.

In some embodiments, personnel may manage settings of the softwareand/or interface 700 with respect to a particular venue (e.g., astadium) such as by utilizing the “Stadium Management” screen shown inFIG. 7C. According to some embodiments, such as by utilizing a“Concession Management” screen depicted in FIG. 7D, settings regarding aparticular fulfillment station/facility (e.g., the “Concession #112”)may be entered, viewed, and/or modified. In some embodiments, such as inthe case that the interface 700 is utilized to facilitate and/or managecustomer orders, a “Concession Fulfillment” screen such as shown in FIG.7E may be displayed via the interface 700. The screen may include, forexample, a listing of any orders assigned to the particular fulfillmentfacility (e.g., the Coca-Cola® order from the example of FIG. 6EE)and/or a “Start Order” button that may be utilized to begin theprocessing of the order at the fulfillment facility.

According to some embodiments, such as in the case that the “StartOrder” button is selected and/or activated and/or the order “AKJ” isselected, the interface 700 may display a screen with order details(e.g., to facilitate initiation of order preparation/fulfillment) andthe status of the order may be changed to indicate that the order isbeing prepared (e.g., “Progress”; as shown in FIG. 7F). In someembodiments, such as in the case that the order is ready, the status ofthe order may be updated as shown in FIG. 7G to indicate that the orderis ready. According to some embodiments, such as in the case that the“Checkout” button is selected, a pop-up screen such as shown in FIG. 7Hmay be provided to prompt the personnel to verify the desire toclose-out the order—e.g., upon order fulfillment such as order pickup ordelivery.

In some embodiments, the interface 700 may be utilized to manageinventory data for refreshment products (e.g., sodas and chips) offeredfor sale via the particular fulfillment facility, as depicted in FIG.7I. Such information may be updated by POS personnel, for example, andstored in one or more databases (e.g., that may be accessible to acontroller that allocates orders to fulfillment stations based at leastin part on inventory of products). According to some embodiments, theinterface 700 may also or alternatively be utilized to manageinformation indicative of inventory of merchandise, as shown in FIG. 7J.

While various components of the interfaces 600, 700 have been describedwith respect to certain labels, layouts, headings, titles, and/orconfigurations, these features have been presented for reference andexample only. Other labels, layouts, headings, titles, and/orconfigurations may be implemented without deviating from the scope ofembodiments herein. Similarly, while a certain number of tabs,information screens, form fields, and/or data entry options have beenpresented, variations thereof may be practiced in accordance with someembodiments.

F. Additional Embodiments

1. Promotions and Pricing

In some embodiments, promotions may be “pushed” or served to customer ata venue based on real-time events occurring at the venue. Promotions forspecial items and/or certain products may, for example, be output tocustomers based on game events, scores, and/or other dynamic events atthe venue. In some embodiments, dynamic promotion(s) may be sent toconsumers based on actual sales results during an event/game and/orbased on current, real-time inventory and/or predicted nature of demand.In some embodiments, products may be promoted to customers dynamicallybased on expiration dates and/or times to reducing spoilage by promotingproducts approaching expiration. In some embodiments, available historicvenue merchandise and/or food sales data (by product category andseat/section number) may be utilized to forecast and/or set ticketprices (e.g., ticket and/or season ticket prices may be based at leastin part on product and/or service sales data for certain seats,sections, or even customers or types of customers—e.g., highermerchandise sales sections may warrant decreased ticket prices since thevenue is making good money on the seats already). In some embodiments,different customers within a common event, stadium, and/or other venuemay be offered different pricing for the same (or similar products)based on profile information (e.g. students vs. alumni; east section vs.west section; home team vs. visiting team, season ticket holder vs. cashticket). In some embodiments, pricing may be dynamically rendered basedon time of game, outcome of game or event or funded and/or subsidized bya third-party. In some embodiments, available historic venue sales data(e.g., by product category and seat/section number) may be utilized toinfluence seat upgrade offers to season ticket holders.

According to some embodiments, a robust, dynamic mechanism for areal-time application of various promotions within a remote electronicordering system is provided. Such a mechanism may allow, for example, areal-time control for application of various promotions available in thesystem, such as, but not limited to: (i) an ability to apply differenttypes of promotions such as percent variable, percent variable with cap,percent variable with floor, fixed price amount, and/or certain productpremium items available in the service provider's menu, and premiumproduct items supplied by the third party; (ii) an ability to applypromotional discounts to different basis, such as per order, perspecific SKU item, per specific spending limit, etc.; (iii) an abilityto differentiate and validate various promotions by events, portions ofevents (e.g., post-half-game), dates, times, promo codes, etc.; (iv) anability to process conditional promotions such as next order, firstorder, orders over a certain price threshold amount, etc.; (v) anability to either redeem promo codes generated via various mediums(e.g., e-mail, text message, newspaper, web, TV, radio, etc) or autoredeem when certain conditions are met; and/or (vi) an ability to varyapplication of promotions by location information such as region/states,stadium, venue type, event, event type, concession stand, customer,stadium seat section and row, service provider, product category andproduct itself, etc.

In some embodiments the “moment of the game” (e.g., impulse) may beleveraged to sell memorable event merchandise. For example: Jeter hits3,000th hit—limited edition shirt—can only get by being at game, limitednumber. Merchandise could be specific price point or could be auctioned.In some embodiments, the system tracks event(s) (or plays) at game,stores event(s) and/or allows individual or friends of individuals topurchase merchandise or memorabilia based on that event. Item(s) couldbe limited in number or could be open number. Purchases could be limitedto certain window of time from when event occurs or could also be open.For example, items could be purchased only within the 7th inning (rightbefore Yankees win World Series) or could be open.

In some embodiments, events can use stats from sport or event to createspecific new “events”; e.g., rookie of year stats, pitched a no-hitter(examples of when records are broken or achieved). Yankees are about towin World Series—be the first 200 people to buy limited edition WorldSeries hat. Could be signed by players, special medallion or limitededition. Could apply to college/football/professional

2. Purchasing

In some embodiments, subscription pricing of food and/or beverage may beoffered. Customers may be offered, for example, the ability to purchasea subscription (for fixed or variable pricing) that gives consumersaccess to special pricing for food and beverage items withinstadium/arena or event for one or multiple events. In some embodiments,some products ordered and sold via a mobile app can have differentservice requirements such as alcohol policy or product must be heated orchilled to certain temperature. In some embodiments, these servicerequirements must be adhered by the system accepting and fulfillingorders. Such enforcement can be built as a subsystem that monitorsproduct service requirements during either check-out or order submissionprocess or both and do one of the following three things (based on theAlcohol policy enforcement type): (a) ‘Inform’: this is a less intrusiveenforcement that includes a few purchase in-path messages that informconsumers about the alcohol policy in effect at a particularvenue/event; (b) ‘Warn’: this is a more intrusive enforcement thatincludes a pop-up message or notification message sent to consumers thatinform them about the alcohol policy in effect at a particularvenue/event and requires an active awareness confirmation of the statedpolicy; (c) ‘Restrict’: this is the most restrictive enforcement thatincludes both hard validation and prevention of orders from submissionthat exceed allowable alcohol item limit.

In some embodiments, one of the alcohol policy requirements is a momentof time after which a food service provider should stop selling thealcohol containing beverage during an event. In order to enforce such arequirement, the system can provide a master switch capability as partof the concession/event management portal. It can be achieved as follows(for example): (i) place a dedicated action-button on the managementportal where an access to it is granted only to the event manager, (ii)by clicking this button system will create a new record (either stop orresume selling alcohol—the text on the button should alternate betweenStop and Resume) in the new database; (iii) the latest (by time stamp)record from this data table should be passed to the App so that whenconsumer view an alcohol containing item on the menu selection screen wecan either remove the <select> button (or its equivalent) from thescreen or provide a note that this item is no longer available forselection due to alcohol policy in effect, or both; in any event, thesystem should not allow an order to be placed with any alcohol item init post stop event timestamp; and/or (iv) use shopping cart validationmechanism on the shopping cart screen as follows: assess shopping carton items containing alcohol and if contains them, then verify the latesttimestamp record for subject event, and if it is to be stopped (vs.resumed) then notify consumer via message on the same screen and allowhim to remove selected alcohol items but leave non-alcohol items in thecart. In any event, system would not allow an order to be placed withany alcohol item in it post-stop event timestamp.

In some embodiments, a robust, real-time, dynamic mechanism for feecalculation and/or splitting within a remote electronic ordering systemis provided. Such a mechanism may allow, for example, real-time controlof how to calculate various fees, such as, but not limited to: (i) anability to calculate fee as a straight variable percent of the itemprice; (ii) an ability to calculate fee as a variable percent of theitem price subject to either a flat cap or floor amount; (iii) anability to calculate fee as a flat add-on amount; (iv) an ability tolevy more than one fee (delivery add-on fee, for instance); (v) anability to have different basis for calculating variable fee (item ororder, for example); and/or (vi) an ability to vary fee by stadium,venue type, event, event type, concession stand, stadium seat sectionand row, service provider, product category and product itself.

In some embodiments, to enable a flexibility of the fee calculationcontrol, the system would utilize a database where all dial settings arestored. These settings may include the following: (i) fee_calculation_id(bgint); (ii) fee_name (varchar); (iii) fee_description (varchar); (iv)fee_type_id (1—straight variable; 2—variable with cap; 3—variable withfloor; 4—flat amount—can be stored in to new fee_type_lookup table); (v)fee_basis_id (1—for item-based calc; 2—order-based calc—can be stored into new fee_basis_lookup table); (vi) fee_value (decimal.2)—decimal ishelpful for using P-type value; but for F-type value we would use lowestcurrency denomination—cents in US; (vii) fee_value_type (char)—P—forpercent; F—for flat or fixed); (viii) fee_cap_value_amt (int—can beNULL); and/or (ix) fee_floor_value_amt (int—can be NULL).

Other fields in such a table may, for example, define the dimensions bywhich differentiation and control of the fee calculation parametersdefined in the above fields is accomplished: (i) store_regexp_id (forREGEXP use); (ii) venue_type_regexp_id (for REGEXP use); (iii)event_regexp_id (for REGEXP use); (iv) event_type_regexp_id (for REGEXPuse); (v) concession_stand_regexp_id (for REGEXP use); (vi)stadium_section_regexp_num (for REGEXP use); (vii)stadium_row_regexp_num (for REGEXP use); (viii)service_provider_regexp_id (for REGEXP use); (ix)product_category_regexp_id (for REGEXP use); (x) product_reg_exp_id (forREGEXP use); (xi) active_Flag (var—Y or N); (xii) effective_time(bigint); and/or (xiii) discontinue_time (bigint).

In some embodiments, a fee calculation process may have two main steps(example is based on StadiumVIP mobile app system): (1) upon customerentering the stadium or event (submitting his seat information),currently among other things, system validates his seat location andassign the concession stands available to a customer at the event. Oncethis is complete and prior to allowing customer's entrance, we have toadd one more data retrieval request (via query from database tabledescribed above) and send all retrieved fee records (normally one or tworecords) to consumer's device along with entrance permission data (or ifthe fee calc resides only on the server side this query can be doneduring fee calc itself); The query should contain the following fieldfilters (all this data elements related to a particular customer'sstadium entrance are readily available to the system at this point):Store_regexp_id; Venue_type_regexp_id; Event_regexp_id;Event_type_regexp_id; Concession_stand_regexp_id;Stadium_section_regexp_n um; Stadium_row_regexp_num;Service_provider_regexp_id; Active_Flag; Effective_time;Discontinue_time; (2) when customer selects items from the menu screenand click <Go To Cart> button, system would have to initiate acalculation of appropriate fee(s) for the shopping cart at hand.

In some embodiments, if more than one applicable fee record returnedfrom the fee calculation control table, then system would evaluate andcalculate each fee record separately by utilizing one of the methoddescribed above. At the end, system would just sum all resulted fees asthey are additive for the shopping cart at hand. However, system maykeep each fee total separately in order to state them separately on allcommunications with both customers and providers (check-out screen,emails, printed receipt, and the concession stand management portal).

In some embodiments, customers may split and/or share orders. Multipleorders may be grouped together to be paid by a single customer, forexample, and/or a single order may be paid utilizing multiple paymentmethods (e.g., split 50/50 between two credit cards of two friends). Insome embodiments, orders may be scheduled for specific times, dates,and/or events (e.g., every time a home-run is hit). In some embodiments,scheduled orders and/or other orders may comprise “re-orders” similar toprescription refills or the re-dialing of a telephone in the sense thatorder data and details are saved and accessed for the new order withoutrequiring re-entry of data. This may be advantageous, for example, byallowing a customer at a venue to press a button (e.g., “re-order”) tosimply submit a new order similar and/or identical to a previous order.

3. Network Usage

A lot of today's real-time transactional systems rely on a dedicatedchannel or network bandwidth to process the orders. Most of thesesystems are usually processing orders from a few aggregators that areconnected to a service provider or supplier's inventory via dedicatednetwork lines/channels. Travel industry reservation systems being oneexample whereby a few on-line travel agencies connected to theairline/hotel inventory supply by the dedicated network lines. However,in truly mass market transactional systems achieving the real-timeordering and fulfillment capability especially during the peak demandtime period is almost impossible to do due to limited, though dedicatedin some cases, network bandwidth. Examples of this deficiency areplenty, including a well publicized order systems failure at both AT&Tand Apple during the launch of i-Phone 4 product in early 2010.

In some embodiments, transactional data transmissions (from an orderinitiation points to order processing and fulfillment points and back)utilizing various communication vehicles available today in moderncommunication network infrastructure may be dynamically managed. As anexample, a mobile phone application is the software residing on themobile phone/device that allows consumers attending various games/eventsto place real-time orders for products (such as food, drinks, andmerchandise) via wireless carriers' network to service provider'sorder-processing and fulfillment systems (all together the systemsback-end). By placing an order, a consumer generates transactional datatransmission that includes, among other things, menu item identificationsuch as product id and description, menu item price, ordered quantity ofeach item, total order amount to be charged to his/her credit card, etc.In return, the back-end system generates transactional data transmissionthat includes order receipt confirmation, order status change (ready,on-hold, delayed, etc), and order fulfillment confirmation.

These data transmissions are sent to/from consumers via their devices'wireless carrier network. It's known that wireless carrier networkcapacity (bandwidth) among other things depends on the wirelesscommunication cell towers (a.k.a. base station) capacity placed in thevicinity of mobile phone holders. As stadiums/arenas usually located onthe outskirts of most cities/towns, the wireless tower coverage in theseareas is usually sparse. This situation is aggravated even further when40,000 to 100,000 event attendees want to use their mobile phone duringa half break of the football game, for example. During such congestednetwork times, the tower's capacity is so limited that making a phonecall or regular data transmission is almost definitely not possible.

While these networks are engineered to handle increased volume oftraffic, the sheer number of calls or/and picture/video/email datatransmission would be far greater than bandwidth capacity for voice/datacommunications in the affected areas. Thus, enabling consumers to submittheir real-time orders via a mobile device, even under suchcircumstances, may be of great importance and can be achieved byutilizing the embodiments described herein.

Although with voice-based phone services or data services being almostentirely unavailable due to TCH (Traffic Channels) saturation duringspiked bandwidth demand, the SMS (short message service) messages wouldbe still successfully received in even the most congested regions/areasbecause the control channels (CCH) responsible for their delivery wouldremain available. Accordingly, SMS messaging is now viewed by many as areliable (almost guaranteed) method of communication (or communicationvehicle) when all other means appear unavailable.

Some embodiments utilize this architectural benefit of SMS network atmany carriers by dynamically selecting a specific communication vehicle(from among data transmission vehicle, email transmission vehicle, andSMS transmission vehicle) to be engaged in sending real-timetransactional data from customer's mobile device to the back-end systemand back to consumers in automated fashion based on one or many inputvariables such as expected cost of data transmission, data expiration orage time, signal strength, packet or signal drop-off rate, etc.

IV. Networking

A. System Overview

Turning to FIG. 8, a block diagram of a system 800 according to someembodiments is shown. In some embodiments, the system 800 may comprise acontroller 810 (such as the controller 110, 510 of FIG. 1 and/or FIG. 5herein), a scoreboard 816 (such as the output device 418 of theapparatus 410 of FIG. 4 herein), a plurality of mobile customer devices830 a-d (such as the mobile customer devices 130, 530 of FIG. 1 and/orFIG. 5 herein), a network 850 (such as the network 150 of FIG. 1herein), and/or a venue 880. According to some embodiments, the network850 may comprise communication links to the controller 810, thescoreboard 816, and/or any or each of the plurality of mobile customerdevices 830 a-e, any or all of which may be communicatively connected toand/or via the communication links of the network 850. According to someembodiments, fewer or more components and/or various configurations ofthe depicted components may be included in the system 800 withoutdeviating from the scope of embodiments described herein. In someembodiments, the components 810, 816, 830, 850, 880 may be similar inconfiguration and/or functionality to similarly named and/or numberedcomponents as described with reference to the system 100 of FIG. 1, themethods 200, 300 of FIG. 2 and/or FIG. 3, and/or the processes 500, 502of FIG. 5A and/or FIG. 5B, herein.

According to some embodiments, the system 800 may be configured tomanage and/or facilitate communications between the various components810, 816, 830, 850 to effectuate networking betweenfans/customers/attendees (not explicitly shown, but associated with themobile customer devices 830 a-e, for example) of the venue 880 (and/orof events held therein). The first mobile customer device 830 a may, forexample, communicate with the second mobile customer device 830 b viathe network 850. In some embodiments, the communication may involveissuing a friendly “challenge” to another fan of the venue, sharingmedia captured from a location of the first mobile customer device 830a, transmitting an indication of a gift (e.g., a gifted item from avenue fulfillment facility), communications that facilitate and/orcomprise an interactive gaming session between fans, and/or otherinter-fan communications.

In some embodiments, any or all of the mobile customer devices 830 a-emay also or alternatively communicate outside of the network 850. Thefirst mobile customer device 830 a may communicate directly with thefourth mobile customer device 830 d, for example, such as viaBluetooth®, IR, RF, and/or other short-range and/or directcommunications means (e.g., a cable). According to embodiments, thethird mobile customer device 830 c may communicate with the fifth mobilecustomer device 830 e which may, for example, be located outside of thevenue 880. In some embodiments, any or all communications amongst themobile customer devices 830 a-e may be routed through and/or processedby the controller 810. According to some embodiments, the controller 810may select certain communications and/or communication content fordisplay of the scoreboard 816. In such a manner, for example,fan-generated and/or selected content may be displayed via thescoreboard 816 at the venue 880.

While the network 850 is depicted in FIG. 8 as a single object, thenetwork 850 may comprise any number, type, and/or configuration ofnetworks that is or becomes known or practicable. According to someembodiments, the network 850 may comprise a conglomeration of differentsub-networks and/or network components interconnected, directly orindirectly, by the components 810, 816, 830, 850 of the system 800. Thenetwork 850 may comprise one or more cellular telephone networks withcommunication links between the first mobile customer device 830 a andthe second mobile customer device 830 b, for example, and/or maycomprise the Internet, with communication links between the controller810 and the third mobile customer device 830 c, for example.

In some embodiments, the network 850 may comprise a LAN (wireless and/orwired) with communication links between the controller 810 and any orall of the mobile customer devices 830 a-e (such as in the case that anysuch devices 810, 830 a-e are located within close proximity—e.g., thesame building, structure, and/or area, such as the venue 880). In someembodiments, the network 850 may comprise direct communications linksbetween components 810, 816, 830 of the system 800. In some embodiments,the network 850 may comprise one or many other links or networkcomponents other than those depicted in FIG. 8. Any or all of the mobilecustomer devices 830 a-d may be connected to the controller 810 viavarious cell towers, routers, repeaters, ports, switches, and/or othernetwork components that comprise the Internet and/or a cellulartelephone (and/or Public Switched Telephone Network (PSTN)) network, andwhich comprise portions of the network 850.

B. Methods

Turning to FIG. 9, a flow diagram of a method 900 according to someembodiments is shown. In some embodiments, the method 900 may beperformed and/or implemented by and/or otherwise associated with one ormore specialized computerized processing devices (e.g., the controller110, 510, 810 and/or the mobile customer devices 130, 530, 830 of FIG.1, FIG. 5A, FIG. 5B, and/or FIG. 8 herein), specialized computers,computer terminals, computer servers, computer systems and/or networks(e.g., the network 150, 850 of FIG. 1 and/or FIG. 8 herein), and/or anycombinations thereof. In some embodiments, the method 900 may beembodied in, facilitated by, and/or otherwise associated with variousinput mechanisms and/or interfaces such as the interfaces 600, 700described with respect to FIG. 6A, FIG. 6B, FIG. 6C, FIG. 6D, FIG. 6E,FIG. 6F, FIG. 6G, FIG. 6H, FIG. 6I, FIG. 6J, FIG. 6K, FIG. 6L, FIG. 6M,FIG. 6N, FIG. 6O, FIG. 6 P, FIG. 6Q, FIG. 6R, FIG. 6S, FIG. 6T, FIG. 6U,FIG. 6V, FIG. 6W, FIG. 6X, FIG. 6Y, FIG. 6Z, FIG. 6AA, FIG. 6BB, FIG.6CC, FIG. 6DD, FIG. 6EE, FIG. 6FF, FIG. 6GG, FIG. 6HH, FIG. 6II, FIG.6JJ, FIG. 7A, FIG. 7B, FIG. 7C, FIG. 7D, FIG. 7E, FIG. 7F, FIG. 7G, FIG.7H, FIG. 7I, and/or FIG. 7J herein.

In some embodiments, the method 900 may comprise receiving, (e.g., by anelectronic controller) from a first mobile device of a first attendee ofan event at a venue, an indication of a request to challenge a secondattendee of the event, at 902. A “challenge”, as the term is utilizedherein, may generally refer to any type of competition betweenfans/customers/attendees. Examples of challenges include but are notlimited to, for example, a “bet” that certain events at the event/venuewill or will not occur and/or a trivia question and/or other gamingcompetitions. In some embodiments, for example, a fan may challenge afriend at the venue, a random fan, and/or a computer (e.g., ArtificialIntelligence (AD). To identify the recipient of the challenge, the firstattendee may enter a seat and/or section number, handle or nickname,friend and/or fan identifier, and/or select and/or take an image of thedesired challenge recipient. In some embodiments, a system associatedwith the venue may suggest and/or select challenge recipients on behalfof the fan. Fans with similar interests (e.g., rooting for the sameteam), similar skill levels (e.g., for skill-based game challenges),and/or fans proximate to the challenging fan (e.g., fans in the samesection and/or nearby or adjacent seats) may, for example, be selectedand/or suggested by the system. In some embodiments, the challengerequest may include an identification and/or selection or suggestion ofa particular prize (or a menu of prize options) which the winner of thecompetition may earn.

According to some embodiments, the method 900 may comprise transmitting,(e.g., by the electronic controller and/or in response to the receivingof the indication of the challenge request) to a second mobile device ofthe second attendee of the event, an indication of the challengerequest, at 904. In some embodiments, such as in the case that the twoattendees are proximate to each other and/or in the case that the firstattendee selects the second attendee as a recipient of the challenge,the transmitting may be accomplished directly from the first mobiledevice to the second mobile device (e.g., via Bluetooth®, IR, RF, and/orother short-range and/or line-of-sight communication methods). Accordingto some embodiments, such as in the case that the system selects thesecond attendee and/or in the case that the second attendee is remotefrom the first attendee, the transmitting may be conducted throughand/or via a controller and/or network.

In some embodiments, the method 900 may comprise receiving, (e.g., bythe electronic controller) from the second mobile device of the secondattendee of the event, an indication of an acceptance of the challengerequest, at 906. In some embodiments, the acceptance may include anacceptance of the particular prize for which the competition isconducted and/or may include a counter-offer or even an “upping” of theante.

According to some embodiments, the method 900 may comprise determining,(e.g., by the electronic controller and/or in response to the receivingof the indication of the acceptance of the challenge request) based on(i) stored challenge criteria relating to possible occurrences at theevent and (ii) an actual occurrence at the event, whether either of thefirst or second attendees has won the challenge, at 908. In the casethat the challenge is similar to a “bet”, for example, the controller(and/or other device) may store an indication of a rule defining the“bet”. The first attendee may “wager” (e.g., offer to buy) a Pepsi® forthe second attendee if a first team wins a game conducted at the venue,for example, in exchange for the second attendee agreeing to purchase aPepsi® (or other product) for the first attendee if a second team winsthe game at the venue. An application running on one or more of themobile devices and/or the controller may store a trigger based uponwhich team wins the game at the venue and may determine based on suchinformation (e.g., when it becomes available), which attendee (ifeither) has won the challenge. In some embodiments, the loser isautomatically debited for the price of the particular prize and thewinner is automatically credited for an amount equal to the particularprize and/or is otherwise provided the particular prize (e.g., given aredemption code and/or having the prize delivered to the winner).

In some embodiments, the method 900 may comprise selecting (e.g., by theelectronic controller) a fulfillment facility at the venue that iscapable of providing a particular prize to the winner of the challenge,at 910. As described in reference to the procedure at 206 of the method200 from FIG. 2, for example, the controller may utilizespecially-programmed logic and/or rules to select one of a plurality ofavailable fulfillment stations via which the “order” for the prizeshould be fulfilled.

According to some embodiments, the method 900 may comprise causing(e.g., by the electronic controller) the particular prize to be providedto the winner of the challenge via the selected fulfillment facility atthe venue, at 912. As described herein with reference to productordering and/or sales at venues, for example, the winning attendee maypick up the prize at the selected fulfillment station or may have theprize delivered to the attendee (e.g., by a hocker or runner).

In some embodiments, challenges may include more than two attendees,customers, and/or fans (whether at the venue or not). Multi-party gamesmay be conducted and/or facilitated by the controller, for example.According to some embodiments, multiple attendees may organize (or beorganized) into one or more teams. Fans may organize or be categorizedinto (e.g., by the controller and based on fan data), for example, teamsmimicking the professional teams that may be playing a game at the venue(e.g., the Orioles® v. the Yankees®). In some embodiments, third-partysponsors may subsidize and/or provide the challenge prize. The challengeitself may be sponsored by Pepsi®, for example, and/or may includechallenge results being displayed via a scoreboard at the venue and/ordistributed via a social networking site such as Facebook®.

According to some embodiments, fans may define “virtual” geo-cacheprizes utilizing the systems described herein and/or as part of achallenge. A fan utilizing a mobile device at a venue, for example, maytag one or more locations at the venue to define them as virtualgeo-caches of various objects and/or prizes. In such an embodiment,other fans, as part of the challenge, may be required to find the“hidden” objects and/or virtual products. In some embodiments, such asin the case that a challenge participant locates a hidden virtualproduct and/or prize, the system may award the “hidden” virtual prize tothe participant by crediting the participant an amount equal to a priceof the corresponding actual product and/or may otherwise provide a unitof the corresponding actual product to the participant. In someembodiments, location information descriptive of a location of theparticipant may be compared to stored virtual geo-cache information toverify that the hidden item has been “found”. In some embodiments,virtual items may be placed and/or gifted without the need for theplacing party/gifting party to travel to the actual location where thevirtual item is placed. In some embodiments, the geo-cached locationscan be anywhere—e.g., not limited to within a venue. One or more fansand/or other people may place virtual products at remote locations suchas on top a mountain, for example, without ever having visited thelocation. In such a manner, virtual gifts (e.g., that are redeemable foractual corresponding products) may be placed for a mountain climber suchthat the climber earns great rewards (e.g., many gifts from manysupporters of the climb) upon location verification and matching to thevirtually-placed items.

V. Apparatus

Turning to FIG. 10, a block diagram of an apparatus 1030 according tosome embodiments is shown. In some embodiments, the apparatus 1030 maybe similar in configuration and/or functionality to the controllers 110,510, 810, the fulfillment devices/facilities 170, 570, and/or the mobilecustomer devices 130, 530, 830 of FIG. 1, FIG. 5, and/or FIG. 8 herein.The apparatus 1030 may, for example, execute, process, facilitate,and/or otherwise be associated with the methods 200, 300, 900 of FIG. 2,FIG. 3, and/or FIG. 9 and/or with the process 500, 502 of FIG. 5A and/orFIG. 5B herein. In some embodiments, the apparatus 1030 may comprise aprocessor 1032, an input device 1034, an output device 103, acommunication device 1038, and/or a memory device 1040. Fewer or morecomponents and/or various configurations of the components 1032, 1034,1036, 1038, 1040 may be included in the apparatus 1030 without deviatingfrom the scope of embodiments described herein.

According to some embodiments, the processor 1032 may be or include anytype, quantity, and/or configuration of electronic and/or computerizedprocessor that is or becomes known. The processor 412 may comprise, forexample, an Intel® IXP 2800 network processor or an Intel® XEON™Processor coupled with an Intel® E7501 chipset, available from Intel®Corporation of Santa Clara, Calif. In some embodiments, the processor1032 may comprise an electronic processor such as an Intel® Core™ 2 DuoP8600 CPU also available from Intel® Corporation of Santa Clara, Calif.In some embodiments, the processor 1032 may execute instructions, suchas instructions specially programmed into and/or for the processor 1032.The execution of the specially-programmed instructions may, for example,enable and/or facilitate the apparatus 1030 to operate in accordancewith embodiments as described herein.

In some embodiments, the processor 1032 may comprise multipleinter-connected processors, microprocessors, and/or micro-engines.According to some embodiments, the processor 1032 (and/or the apparatus1030 and/or other components thereof) may be supplied power via a powersupply (not shown) such as a battery, an AC source, a DC source, anAC/DC adapter, solar cells, and/or an inertial generator. In the casethat the apparatus 1030 comprises a server such as a blade server,necessary power may be supplied via a standard AC outlet, power strip,surge protector, and/or UPS device.

In some embodiments, the input device 1034 and/or the output device 1036are communicatively coupled to the processor 1032 (e.g., via wiredand/or wireless connections, traces, and/or pathways) and they maygenerally comprise any types or configurations of input and outputcomponents and/or devices that are or become known, respectively. Theinput device 1034 may comprise, for example, a keyboard that allows anoperator of the apparatus 1030 to interface with the apparatus 1030(e.g., by an operator of a mobile computing device, such as to implementand/or interact with embodiments herein to purchase products at venuesand/or conduct networking between fans). The output device 1036 may,according to some embodiments, comprise a display screen and/or otherpracticable output component and/or device. The output device 1036 may,for example, provide information, data, and/or images that permit acustomer (e.g., a fan and/or event attendee) to purchase products at avenue and/or network (e.g., produce a customized event blog) with othercustomers. According to some embodiments, the input device 1034 and/orthe output device 1036 may comprise and/or be embodied in a singledevice such as a touch-screen monitor.

In some embodiments, the communication device 1038 may comprise any typeor configuration of communication device that is or becomes known orpracticable. The communication device 1038 may, for example, comprise aNIC, a telephonic device, a cellular network device, a router, a hub, amodem, and/or a communications port or cable. In some embodiments, thecommunication device 1038 may be coupled to provide data to a centralcontroller and/or to mobile customer devices, such as in the case thatthe apparatus 1030 is utilized by a customer of a venue to purchaseproducts from and/or at the venue and/or conduct venue-related socialnetworking via a customer's wireless and/or mobile device. According tosome embodiments, the communication device 1038 may also oralternatively be coupled to the processor 1032. In some embodiments, thecommunication device 1038 may comprise an IR, RF, Bluetooth™, and/orWi-Fi® network device coupled to facilitate communications between theprocessor 1032 (and/or the apparatus 1030) and another device (such asthe controller 110, 510, 810 and/or the fulfillment devices 170 a-n, 570of FIG. 1, FIG. 5A, FIG. 5B, and/or FIG. 8 herein).

The memory device 1040 may comprise any appropriate information storagedevice that is or becomes known or available, including, but not limitedto, units and/or combinations of magnetic storage devices (e.g., a harddisk drive), optical storage devices, and/or semiconductor memorydevices such as RAM devices, ROM devices, SDR-RAM, Double DDR-RAM,and/or PROM. The memory device 1040 may, according to some embodiments,store one or more of stadium purchase instructions 1042-1 and/or stadiumnetworking instructions 1042-2. In some embodiments, the stadiumpurchase instructions 1042-1 and/or stadium networking instructions1042-2 may be utilized by the processor 1032 to provide outputinformation via the output device 1036 and/or the communication device1038 (e.g., transmitting of the challenge indication received at 902and/or transmitting of the challenge acceptance received at 906 of themethod 900 of FIG. 9).

According to some embodiments, the stadium purchase instructions 1042-1may be operable to cause the processor 1032 to access and/or processpersonal data 1044-1. Personal data 1044-1 received via the input device1034 and/or the communication device 1038 may, for example, be analyzed,sorted, filtered, decoded, decompressed, ranked, scored, plotted, and/orotherwise processed by the processor 1032 in accordance with the stadiumpurchase instructions 1042-1. In some embodiments, personal data 1044-1may be utilized by the processor 1032 to facilitate and/or conductprocesses and/or methods in accordance with the stadium purchaseinstructions 1042-1 to facilitate and/or effectuate a customer'spurchase of products and/or services from (or via) a venue as describedherein. The stadium purchase instructions 1042-1 may, in someembodiments, interface with an application stored on and/or executed bya customer's mobile phone, for example, to facilitate the purchaseand/or delivery of venue merchandise and/or refreshments from acustomer's seat (or other location).

According to some embodiments, the stadium networking instructions1042-2 may be operable to cause the processor 1032 to access and/orprocess one or more of the personal data 1044-1, friend data 1044-2,and/or media data 1044-3. Personal data 1044-1, friend data 1044-2,and/or media data 1044-3 received via the input device 1034 and/or thecommunication device 1038 may, for example, be analyzed, sorted,filtered, decoded, decompressed, ranked, scored, plotted, and/orotherwise processed by the processor 1032 in accordance with the stadiumnetworking instructions 1042-2. In some embodiments, personal data1044-1, friend data 1044-2, and/or media data 1044-3 may be utilized bythe processor 1032 to facilitate and/or conduct processes and/or methodsin accordance with the stadium networking instructions 1042-2 tofacilitate, manage, and/or route or otherwise process communicationsbetween and/or amongst customers as described herein. The stadiumnetworking instructions 1042-2 may, in some embodiments, interface withan application stored on and/or executed by a customer's mobile phone,for example, to facilitate networking between the customer and othercustomers at (e.g., other customers of the venue), associated with(e.g., third-party sponsors and/or sports organizations or newsorganizations), and/or remote from the venue (e.g., friends and/orfamily not attending the venue).

In some embodiments, the personal data 1044-1 may comprise any datadescriptive of an attribute or characteristic of a customer. Personaldata 1044-1 may be acquired during a registration processes (e.g., fromthe customer), for example, and may comprise identifying informationsuch as address, name, e-mail address, preferences, payment accountsand/or information, passwords, etc. In some embodiments, the personaldata 1044-1 may comprise data decretive of the customer that is acquiredvia transactions conducted with the customer. Personal data 1044-1 maycomprise, for example, customer preferences (empirical), sales history,customer “worth” (e.g., expected value), frequency of purchases, and/orprevious or typical ordering locations (e.g., season ticket reserved boxseats). In some embodiments, personal data 1044-1 may compriseinformation descriptive of social networking sites, accounts, profiles,activity, and/or preferences associated with the customer.

According to some embodiments, the friend data 1044-2 may comprise datadescriptive of social networking “friends” of the customer. Such“friends” may, for example, comprise people (and/or customers) withprofiles and/or accounts that are related to the customer's profileand/or account at a social networking website. The friend data 1044-2may, in some embodiments, comprise data descriptive of an attribute orcharacteristic of a friend of the customer. According to someembodiments, the friend data 1044-2 may be similar in compilation to thepersonal data 1044-1, except that it is descriptive of a characteristicassociated with friends of the customer instead of the customerthemselves. In some embodiments, friend data 1044-2 may be pulled (e.g.,harvested) and/or acquired from one or more social networking sitesand/or databases associated with the customer.

In some embodiments, the media data 1044-3 may comprise informationdescriptive of media captured and/or recorder by and/or selected by thecustomer. The media data 1044-3 may, for example, comprise informationdescriptive of and/or defining one or more pictures, sounds, videosegments, graphics, logos, and/or other media that the customer providesvia the apparatus 1030. According to some embodiments, the media data1044-3 may be input and/or recorded by the input device 1034 (e.g., astill and/or video camera). In some embodiments, as described herein,the media data 1044-3 may be utilized to create and/or edit a customizedblog and/or social media page or profile associated with the customer'strip(s) to the venue.

While the apparatus 1030 is described with reference to specificquantities and types of components 1032, 1034, 1036, 1038, 1040,variations in the quantities, types, and/or configurations of thecomponents 1032, 1034, 1036, 1038, 1040 of the apparatus 1030 may beimplemented without deviating from the scope of the embodimentsdescribed herein.

Any or all of the exemplary instructions and data types described hereinand other practicable types of data may be stored in any number, type,and/or configuration of memory device 944 that is or becomes known. Thememory device 1040 may, for example, comprise one or more data tables orfiles, databases, table spaces, registers, and/or other storagestructures. In some embodiments, multiple databases and/or storagestructures (and/or multiple memory devices 1040) may be utilized tostore information associated with the apparatus 1030. According to someembodiments, the memory device 1040 may be incorporated into and/orotherwise coupled to the apparatus 1030 (e.g., as shown) or may simplybe accessible to the apparatus 1030 (e.g., externally located and/orsituated).

VI. Articles of Manufacture

Referring to FIG. 11A and FIG. 11B, perspective diagrams of exemplarydata storage devices 1140 a-b according to some embodiments are shown.The data storage devices 1140 a-b may, for example, be utilized to storeinstructions and/or data such as the stadium ordering instructions422-1, the order allocation instructions 422-2, the customer data 424-1,the fulfillment data 424-2, and/or the order data 424-3 as described inreference to FIG. 4 herein and/or the stadium purchase instructions1042-1, the stadium networking instructions 1042-2, the personal data1044-1, the friend data 1044-2, and/or the media data 1044-3 asdescribed in reference to FIG. 10 herein. In some embodiments,instructions stored on the data storage devices 1040 a-b may, whenexecuted by a processor (such as the electronic processor 412, 1032 ofFIG. 4 and/or FIG. 10), cause the implementation of and/or facilitateany of the various methods 200, 300, 800 of FIG. 2, FIG. 3, and/or FIG.8 and/or the processes 500, 502 of FIG. 5A and/or FIG. 5B, describedherein.

According to some embodiments, the first data storage device 1040 a maycomprise a CD, CD-ROM, DVD, Blu-Ray™ Disc, and/or other type ofoptically-encoded disk and/or other computer-readable storage mediumthat is or becomes know or practicable. In some embodiments, the seconddata storage device 1040 b may comprise a USB keyfob, dongle, and/orother type of flash memory data storage device that is or becomes knowor practicable. The data storage devices 1040 a-b may generally storeprogram instructions, code, and/or modules that, when executed by anelectronic and/or computerized processing device cause a particularmachine to function in accordance with embodiments described herein. Insome embodiments, the data storage devices 1040 a-b depicted in FIG. 11Aand FIG. 11B are representative of a class and/or subset ofcomputer-readable media that are defined herein as “computer-readablememory” (e.g., memory devices as opposed to transmission devices). Whilecomputer-readable media may include transitory media types, as utilizedherein, the term computer-readable memory is limited to non-transitorycomputer-readable media. In some embodiments, the data storage devices1040 a-b depicted in FIG. 11A and FIG. 11B are representative ofprograms, instructions and/or data stored on one or more other types ofcomputer-readable memory devices such as internal or external harddrives and/or flash memory.

VII. Rules of Interpretation

Numerous embodiments are described in this patent application, and arepresented for illustrative purposes only. The described embodiments arenot, and are not intended to be, limiting in any sense. The presentlydisclosed invention(s) are widely applicable to numerous embodiments, asis readily apparent from the disclosure. One of ordinary skill in theart will recognize that the disclosed invention(s) may be practiced withvarious modifications and alterations, such as structural, logical,software, and electrical modifications. Although particular features ofthe disclosed invention(s) may be described with reference to one ormore particular embodiments and/or drawings, it should be understoodthat such features are not limited to usage in the one or moreparticular embodiments or drawings with reference to which they aredescribed, unless expressly specified otherwise.

The present disclosure is neither a literal description of allembodiments of the invention nor a listing of features of the inventionthat must be present in all embodiments.

Neither the Title (set forth at the beginning of the first page of thispatent application) nor the Abstract (set forth at the end of thispatent application) is to be taken as limiting in any way the scope ofthe disclosed invention(s).

The term “product” means any machine, manufacture and/or composition ofmatter as contemplated by 35 U.S.C. §101, unless expressly specifiedotherwise.

The terms “an embodiment”, “embodiment”, “embodiments”, “theembodiment”, “the embodiments”, “one or more embodiments”, “someembodiments”, “one embodiment” and the like mean “one or more (but notall) disclosed embodiments”, unless expressly specified otherwise.

A reference to “another embodiment” in describing an embodiment does notimply that the referenced embodiment is mutually exclusive with anotherembodiment (e.g., an embodiment described before the referencedembodiment), unless expressly specified otherwise.

The terms “including”, “comprising” and variations thereof mean“including but not limited to”, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expresslyspecified otherwise.

The term “plurality” means “two or more”, unless expressly specifiedotherwise.

The term “herein” means “in the present application, including thespecification, its claims and figures, and anything which may beincorporated by reference”, unless expressly specified otherwise.

The phrase “at least one of”, when such phrase modifies a plurality ofthings (such as an enumerated list of things) means any combination ofone or more of those things, unless expressly specified otherwise. Forexample, the phrase at least one of a widget, a car and a wheel means(i) a widget, (ii) a car, (iii) a wheel, (iv) a widget and a car, (v) awidget and a wheel, (vi) a car and a wheel, or (vii) a widget, a car anda wheel.

The phrase “based on” does not mean “based only on”, unless expresslyspecified otherwise. In other words, the phrase “based on” describesboth “based only on” and “based at least on”.

The term “whereby” is used herein only to precede a clause or other setof words that express only the intended result, objective or consequenceof something that is previously and explicitly recited. Thus, when theterm “whereby” is used in a claim, the clause or other words that theterm “whereby” modifies do not establish specific further limitations ofthe claim or otherwise restricts the meaning or scope of the claim.

Where a limitation of a first claim would cover one of a feature as wellas more than one of a feature (e.g., a limitation such as “at least onewidget” covers one widget as well as more than one widget), and where ina second claim that depends on the first claim, the second claim uses adefinite article “the” to refer to the limitation (e.g., “the widget”),this does not imply that the first claim covers only one of the feature,and this does not imply that the second claim covers only one of thefeature (e.g., “the widget” can cover both one widget and more than onewidget).

When an ordinal number (such as “first”, “second”, “third” and so on) isused as an adjective before a term, that ordinal number is used (unlessexpressly specified otherwise) merely to indicate a particular feature,such as to allow for distinguishing that particular referenced featurefrom another feature that is described by the same term or by a similarterm. For example, a “first widget” may be so named merely to allow fordistinguishing it in one or more claims from a “second widget”, so as toencompass embodiments in which (1) the “first widget” is or is the sameas the “second widget” and (2) the “first widget” is different than oris not identical to the “second widget”. Thus, the mere usage of theordinal numbers “first” and “second” before the term “widget” does notindicate any other relationship between the two widgets, and likewisedoes not indicate any other characteristics of either or both widgets.For example, the mere usage of the ordinal numbers “first” and “second”before the term “widget” (1) does not indicate that either widget comesbefore or after any other in order or location; (2) does not indicatethat either widget occurs or acts before or after any other in time; (3)does not indicate that either widget ranks above or below any other, asin importance or quality; and (4) does not indicate that the tworeferenced widgets are not identical or the same widget. In addition,the mere usage of ordinal numbers does not define a numerical limit tothe features identified with the ordinal numbers. For example, the mereusage of the ordinal numbers “first” and “second” before the term“widget” does not indicate that there must be no more than two widgets.

When a single device or article is described herein, more than onedevice or article (whether or not they cooperate) may alternatively beused in place of the single device or article that is described.Accordingly, the functionality that is described as being possessed by adevice may alternatively be possessed by more than one device or article(whether or not they cooperate).

Similarly, where more than one device or article is described herein(whether or not they cooperate), a single device or article mayalternatively be used in place of the more than one device or articlethat is described. For example, a plurality of computer-based devicesmay be substituted with a single computer-based device. Accordingly, thevarious functionality that is described as being possessed by more thanone device or article may alternatively be possessed by a single deviceor article.

The functionality and/or the features of a single device that isdescribed may be alternatively embodied by one or more other deviceswhich are described but are not explicitly described as having suchfunctionality and/or features. Thus, other embodiments need not includethe described device itself, but rather can include the one or moreother devices which would, in those other embodiments, have suchfunctionality/features.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. On the contrary, such devices need only transmit to eachother as necessary or desirable, and may actually refrain fromexchanging data most of the time. For example, a machine incommunication with another machine via the Internet may not transmitdata to the other machine for weeks at a time. In addition, devices thatare in communication with each other may communicate directly orindirectly through one or more intermediaries.

A description of an embodiment with several components or features doesnot imply that all or even any of such components and/or features arerequired. On the contrary, a variety of optional components aredescribed to illustrate the wide variety of possible embodiments of thepresent invention(s). Unless otherwise specified explicitly, nocomponent and/or feature is essential or required.

Further, although process steps, algorithms or the like may be describedin a sequential order, such processes may be configured to work indifferent orders. In other words, any sequence or order of steps thatmay be explicitly described does not necessarily indicate a requirementthat the steps be performed in that order. The steps of processesdescribed herein may be performed in any order practical. Further, somesteps may be performed simultaneously despite being described or impliedas occurring non-simultaneously (e.g., because one step is describedafter the other step). Moreover, the illustration of a process by itsdepiction in a drawing does not imply that the illustrated process isexclusive of other variations and modifications thereto, does not implythat the illustrated process or any of its steps are necessary to theinvention, and does not imply that the illustrated process is preferred.

Although a process may be described as including a plurality of steps,that does not indicate that all or even any of the steps are essentialor required. Various other embodiments within the scope of the describedinvention(s) include other processes that omit some or all of thedescribed steps. Unless otherwise specified explicitly, no step isessential or required.

Although a product may be described as including a plurality ofcomponents, aspects, qualities, characteristics and/or features, thatdoes not indicate that all of the plurality are essential or required.Various other embodiments within the scope of the described invention(s)include other products that omit some or all of the described plurality.

An enumerated list of items (which may or may not be numbered) does notimply that any or all of the items are mutually exclusive, unlessexpressly specified otherwise. Likewise, an enumerated list of items(which may or may not be numbered) does not imply that any or all of theitems are comprehensive of any category, unless expressly specifiedotherwise. For example, the enumerated list “a computer, a laptop, aPDA” does not imply that any or all of the three items of that list aremutually exclusive and does not imply that any or all of the three itemsof that list are comprehensive of any category.

Headings of sections provided in this patent application and the titleof this patent application are for convenience only, and are not to betaken as limiting the disclosure in any way.

“Determining” something can be performed in a variety of manners andtherefore the term “determining” (and like terms) includes calculating,computing, deriving, looking up (e.g., in a table, database or datastructure), ascertaining and the like.

It will be readily apparent that the various methods and algorithmsdescribed herein may be implemented by, e.g., appropriately and/orspecially-programmed general purpose computers and/or computing devices.Typically a processor (e.g., one or more microprocessors) will receiveinstructions from a memory or like device, and execute thoseinstructions, thereby performing one or more processes defined by thoseinstructions. Further, programs that implement such methods andalgorithms may be stored and transmitted using a variety of media (e.g.,computer readable media) in a number of manners. In some embodiments,hard-wired circuitry or custom hardware may be used in place of, or incombination with, software instructions for implementation of theprocesses of various embodiments. Thus, embodiments are not limited toany specific combination of hardware and software

A “processor” generally means any one or more microprocessors, CPUdevices, computing devices, microcontrollers, digital signal processors,or like devices, as further described herein.

The term “computer-readable medium” refers to any medium thatparticipates in providing data (e.g., instructions or other information)that may be read by a computer, a processor or a like device. Such amedium may take many forms, including but not limited to, non-volatilemedia, volatile media, and transmission media. Non-volatile mediainclude, for example, optical or magnetic disks and other persistentmemory. Volatile media include DRAM, which typically constitutes themain memory. Transmission media include coaxial cables, copper wire andfiber optics, including the wires that comprise a system bus coupled tothe processor. Transmission media may include or convey acoustic waves,light waves and electromagnetic emissions, such as those generatedduring RF and IR data communications. Common forms of computer-readablemedia include, for example, a floppy disk, a flexible disk, hard disk,magnetic tape, any other magnetic medium, a CD-ROM, DVD, any otheroptical medium, punch cards, paper tape, any other physical medium withpatterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any othermemory chip or cartridge, a carrier wave, or any other medium from whicha computer can read.

The term “computer-readable memory” may generally refer to a subsetand/or class of computer-readable medium that does not includetransmission media such as waveforms, carrier waves, electromagneticemissions, etc. Computer-readable memory may typically include physicalmedia upon which data (e.g., instructions or other information) arestored, such as optical or magnetic disks and other persistent memory,DRAM, a floppy disk, a flexible disk, hard disk, magnetic tape, anyother magnetic medium, a CD-ROM, DVD, any other optical medium, punchcards, paper tape, any other physical medium with patterns of holes, aRAM, a PROM, an EPROM, a FLASH-EEPROM, any other memory chip orcartridge, computer hard drives, backup tapes, Universal Serial Bus(USB) memory devices, and the like.

Various forms of computer readable media may be involved in carryingdata, including sequences of instructions, to a processor. For example,sequences of instruction (i) may be delivered from RAM to a processor,(ii) may be carried over a wireless transmission medium, and/or (iii)may be formatted according to numerous formats, standards or protocols,such as Bluetooth™, TDMA, CDMA, 3G.

Where databases are described, it will be understood by one of ordinaryskill in the art that (i) alternative database structures to thosedescribed may be readily employed, and (ii) other memory structuresbesides databases may be readily employed. Any illustrations ordescriptions of any sample databases presented herein are illustrativearrangements for stored representations of information. Any number ofother arrangements may be employed besides those suggested by, e.g.,tables illustrated in drawings or elsewhere. Similarly, any illustratedentries of the databases represent exemplary information only; one ofordinary skill in the art will understand that the number and content ofthe entries can be different from those described herein. Further,despite any depiction of the databases as tables, other formats(including relational databases, object-based models and/or distributeddatabases) could be used to store and manipulate the data typesdescribed herein. Likewise, object methods or behaviors of a databasecan be used to implement various processes, such as the describedherein. In addition, the databases may, in a known manner, be storedlocally or remotely from a device that accesses data in such a database.

The present invention can be configured to work in a network environmentincluding a computer that is in communication, via a communicationsnetwork, with one or more devices. The computer may communicate with thedevices directly or indirectly, via a wired or wireless medium such asthe Internet, LAN, WAN or Ethernet, Token Ring, or via any appropriatecommunications means or combination of communications means. Each of thedevices may comprise computers, such as those based on the Intel®Pentium® or Centrino™ processor, that are adapted to communicate withthe computer. Any number and type of machines may be in communicationwith the computer.

The present disclosure provides, to one of ordinary skill in the art, anenabling description of several embodiments and/or inventions. Some ofthese embodiments and/or inventions may not be claimed in the presentapplication, but may nevertheless be claimed in one or more continuingapplications that claim the benefit of priority of the presentapplication. Applicants intend to file additional applications to pursuepatents for subject matter that has been disclosed and enabled but notclaimed in the present application.

1. A method, comprising: receiving, by an electronic controller and froma first mobile device of a first attendee of an event at a venue, anindication of a request to challenge a second attendee of the event;transmitting, by the electronic controller, in response to the receivingof the indication of the challenge request, and to a second mobiledevice of the second attendee of the event, an indication of thechallenge request; receiving, by the electronic controller and from thesecond mobile device of the second attendee of the event, an indicationof an acceptance of the challenge request; determining, by theelectronic controller, in response to the receiving of the indication ofthe acceptance of the challenge request, and based on (i) storedchallenge criteria relating to possible occurrences at the event and(ii) an actual occurrence at the event, whether either of the first orsecond attendees has won the challenge; selecting, by the electroniccontroller, a fulfillment facility at the venue that is capable ofproviding a particular prize to the winner of the challenge; andcausing, by the electronic controller, the particular prize to beprovided to the winner of the challenge via the selected fulfillmentfacility at the venue.
 2. The method of claim 1, further comprising:receiving, by the electronic controller and from the first mobile deviceof the first attendee, an indication of a definition of the challengecriteria relating to possible occurrences at the event.
 3. The method ofclaim 1, further comprising: receiving, by the electronic controller andfrom the first mobile device of the first attendee, an indication of adefinition of the particular prize.
 4. The method of claim 1, furthercomprising: receiving, by the electronic controller and from the secondmobile device of the second attendee, an indication of a definition ofthe particular prize.
 5. The method of claim 1, further comprising:charging, by the electronic controller, the loser of the challenge for aprice of the particular prize.
 6. A method for creating a fan blog,comprising: receiving, by an electronic controller and from a mobiledevice of an attendee of an event at a venue, an indication of mediacaptured at the event; integrating, by the electronic controller andwith the media captured at the event, media obtained from a third-party;and transmitting, by the electronic controller, based on savedpreferences of the attendee, and via a social network associated withthe attendee, an indication of the integrated media to a plurality ofsocial network friends of the attendee.
 7. A network, comprising: (i) afirst communication link to a central electronic controller associatedwith a venue; (ii) a second communication link to a first mobile fandevice operated by a first fan of an event at the venue; and (iii) athird communication link to a second mobile fan device operated by asecond fan of the event at the venue, wherein the network: (a) receives,via the second communication link, an indication of media captured atthe event; (b) transmits, via the first communication link, theindication of media captured at the event; (c) receives, via the firstcommunication link, an indication of an integration of the mediacaptured at the event with third-party media; and (d) transmits, via thethird communication link, an indication of the integration of the mediacaptured at the event with third-party media.